Last modified: 2014-09-25 11:24:16 UTC
There's a few (not too many!) things that need a home, and I think this is a good time to start work on what will become the main entry point for developers to learn about Wikimedia (wiki) projects and Wikimedia (software) products. developer.wikimedia.org The initial portal wouldn't be unlike some of these: * https://developers.google.com/ * https://developers.facebook.com/ * https://dev.twitter.com/ Here's are some very specific use cases that have come up during the Zurich Hackathon that I think would be best served with this: - Where do I find out about the existence of: * gdash.wikimedia.org * graphite.wikimedia.org * noc.wikimedia.org * doc.wikimedia.org * git.wikimedia.org * wikitech.wikimedia.org * irc.wikimedia.org ( * stream.wikimedia.org/rc ) Current solution: None Current workaround for regulars: https://wikitech.wikimedia.org/wiki/Category:Services - Where would I find out about xml dumps? Current solution: None Current workaround for regulars: http://dumps.wikimedia.org/backup-index.html - Where would I find out about pageview count data? Current solution: None Current workaround for regulars: http://dumps.wikimedia.org/ http://dumps.wikimedia.org/other/ http://dumps.wikimedia.org/other/pagecounts-raw/ I'm sure the people from the "Data API & Hub" table from Zurich Hackathon 2014 have more specific stories and use cases. This hub would act as delegate for the following cases (pointing to things on another domain or the same, some of which should probably move to it eventually): * Products Such as: - MediaWiki -> Homepage -> Source code (git repo) -> Documentation (separate portal, on mediawiki.org for now, ultimately linking back to developer.wikimedia.org/mediawiki/{js,php,api} for documentation of individual classes and apis. We already have JS and PHP docs autogenerated for MediaWiki. Docs the API are still hardcoded on mediawiki.org and api.php/help exclusively, we should get API and Hooks documentation onto doc.wikimedia.org as well. See https://www.mediawiki.org/wiki/Requests_for_comment/Documentation_overhaul - VisualEditor -> Source code -> Demo(s) -> Documentation * Data and APIs (APIs that are not related to MediaWiki or individual user-facing products, but Wikimedia services in general, MediaWiki's API is one small part of that) Such as: * page view counts * xml dumps * OAuth? * irc.wikimedia.org ( * stream.wikimedia.org/rc ) * "See also: Wikidata" * Communications - (e.g. link to tech blog, as currently linked from noc.wikimedia.org) - mailing lists
I think all of doc.wikimedia.org can migrate to appropriate paths on this domain. Like: - dev.wikimedia.org/mediawiki/doc/js - dev.wikimedia.org/mediawiki/doc/php - dev.wikimedia.org/mediawiki/doc/api - dev.wikimedia.org/visualeditor/doc - dev.wikimedia.org/visualeditor/demo - dev.wikimedia.org/oojs-ui/doc - dev.wikimedia.org/oojs-ui/demo - dev.wikimedia.org/oojs/doc
I'm in full support of this. As someone working on this https://www.mediawiki.org/wiki/API_Documentation_&_Developer_Hub, I would like this very much.
Initial implementation proposal: - static html wrapped in a lightweight php router for header/footer and nice url handling (e.g. no need to repeat too much for each subdirectory, it can be handled automatically using data and available directories (js,php,api,demo) and versions (master,REL1_23,etc.)), using twitter bootstrap (like doc.wikimedia.org) - all in git (wikimedia/dev-docroot.git?) - deployed via git-deploy The server for it only needs to be behind misc-lb-eqiad and be a git-deploy target. The main changes would come in from people via gerrit/git and deployed periodically. Changes to the auto-generated docs would be build by gallium, and somehow pushed to the web server (they wouldn't be in dev-docroot.git).
Topic related with a session scheduled for tomorrow at 10:30 in the Wikimedia Hackathon: How does the data and developer hub fit into the current documentation https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Schedule#Saturday_May_10
(In reply to Krinkle from comment #0) > * Data and APIs > > Such as: > > * page view counts > * xml dumps > * OAuth? Discovered today that there is such a thing as https://frdata.wikimedia.org as well. To be documented at https://wikitech.wikimedia.org/wiki/frdata.wikimedia.org.
Why not just have dev.wikimedia.org redirect to a page on mediawiki.org. That way people can update it as appropriate easily. >- Where do I find out about the existence of: [..] > * graphite.wikimedia.org Not much point telling people about the existence of a service they are not allowed access to.
(In reply to Krinkle from comment #0) > > developer.wikimedia.org > > The initial portal wouldn't be unlike some of these: > * https://developers.google.com/ > * https://developers.facebook.com/ > * https://dev.twitter.com/ * https://developer.github.com/ * https://developer.yahoo.com/ * http://dev.windows.com/ * http://www.bing.com/dev https://developers.google.com/ https://developers.google.com/maps/documentation/javascript/tutorial https://developers.google.com/maps/documentation/javascript/examples/map-simple
Let's merge this discussion with the work done at https://www.mediawiki.org/wiki/dev.wikimedia.org. Sorry for the duplicity of spaces, which will go away when we merge Bugzilla with Phabricator. We have settled on http://dev.wikimedia.org -- see Name for the 'developer hub' http://fab.wmflabs.org/T488 and URL of the Developer Hub http://fab.wmflabs.org/T490 (In reply to Bawolff (Brian Wolff) from comment #6) > Why not just have dev.wikimedia.org redirect to a page on mediawiki.org. > That way people can update it as appropriate easily. Yes, this is the current plan that you can help fine tuning: Technology selection for the Developer Hub http://fab.wmflabs.org/T491 How to redirect from dev.wikimedia.org http://fab.wmflabs.org/T558
Removing myself from cc on this as I prepare to leave Wikimedia Foundation.
