The Developer Hub must sit somewhere and we need a memorable URL for it. For this we need a name and also a decision on whether it should sit inside mediawiki.org or another existing MediaWiki, or in a site on its own.
Description
Description
Details
Details
- Reference
- fl490
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Fix longstanding bug in git.next_deploy_tag() | repos/releng/scap!224 | dancy | master-I9fb05718a492b1137bd1d841199b51c51352f6b0 | master | |
| builds-builder: bump to 0.0.85-20240109170619-e4596900 | repos/cloud/toolforge/toolforge-deploy!166 | project_1317_bot_df3177307bed93c3f34e421e26c86e38 | bump_builds-builder | main | |
| inject_buildpacks: use shimmed dotnet buildpack | repos/cloud/toolforge/builds-builder!27 | dcaro | use_shimmed_dotnet | main | |
| Section image suggestions pipeline | repos/structured-data/image-suggestions!19 | cparle | T311289-combined | main | |
| Disable skein log collection by default | repos/data-engineering/airflow-dags!226 | milimetric | disable-skein-log-collection | main | |
| Update the mediawiki image to buster-php74-fpm:1.0.0-s1 | repos/releng/cli!203 | ollieshotton | update-mw-image | main | |
| Disable public druid metadata ingestion | repos/data-engineering/airflow-dags!97 | milimetric | disable-public-druid-metadata-ingestion | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Qgil | T101099 Developer Relations Roadmap | |||
| Resolved | Qgil | T113030 Developer Relations quarterly review Jul-Sep 2015 | |||
| Resolved | Qgil | T101100 Engineering Community quarterly goals for July-September 2015 | |||
| Resolved | • Spage | T101441 Goal: Integrate the new Web APIs hub with mediawiki.org | |||
| Resolved | Qgil | T308 A single Developer Hub plan agreed and documented | |||
| Resolved | Qgil | T311 URL of the Developer Hub | |||
| Resolved | Qgil | T309 Name for the 'developer hub' | |||
| Resolved | Qgil | T312 Technology selection for the Developer Hub | |||
| Resolved | None | T310 Requirements for the Developer Hub infrastructure | |||
| Declined | None | T322 Possibility to pair API documentation with user comments |
Event Timeline
Comment Actions
qgil wrote on 2014-08-25 12:56:05 (UTC)
build.wikimedia.org it is. This might be a redirect to another URL marked by the CMS used to power the site, MediaWiki or another.
Comment Actions
qgil wrote on 2014-08-25 19:13:23 (UTC)
... and resolving with dev.wikimedia.org -- reasoning at T492#12.
Comment Actions
marktraceur wrote on 2014-08-26 16:25:05 (UTC)
I posted on the mailing list and I'll echo my concerns here: I don't like that we're naming our data/APIs portal "dev", because I think it presents a minimised view of what we offer developers. We're a free software project, and if dev.wikimedia.org doesn't contain documentation for our actual software, instead of just our externally-facing APIs, in my opinion we will confuse people and possibly lose them in that confusion.
I mentioned on the mailing list that "developer" pages, many of which have been listed in our "external examples" section, have often driven me away from projects when they only contained data/API documentation and did not explain how to work on the software itself. I really don't want Wikimedia to become a project that I would be driven away from.
Comment Actions
qgil wrote on 2014-08-26 20:23:51 (UTC)
This problem can be solved by a prominent box in the dev homepage pointing to what is today https://www.mediawiki.org/wiki/Developer_hub, evolved. (T480) There you will have all the information related to our software projects, where is the source, how to contribute.
At the end we are talking about a namespace within mediawiki.org, the site which contains all the rest of developer information. We just want to offer to the devs that are indeed looking for APIs what they are looking for.
Comment Actions
I cannot edit that comment, but the reasoning can be found in the post-fab-migration T313