https://bugzilla.wikimedia.org/show_bug.cgi?id=65074
Bug ID: 65074
Summary: Set up developer.wikimedia.org portal
Product: Wikimedia
Version: wmf-deployment
Hardware: All
OS: All
Status: NEW
Keywords: tracking
Severity: normal
Priority: Unprioritized
Component: General/Unknown
Assignee: [email protected]
Reporter: [email protected]
Blocks: 2007
Web browser: ---
Mobile Platform: ---
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
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
