Last modified: 2014-09-25 11:24:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T67074, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65074 - Set up portal
Set up portal
Status: NEW
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: tracking
Depends on:
Blocks: tracking
  Show dependency treegraph
Reported: 2014-05-09 14:37 UTC by Krinkle
Modified: 2014-09-25 11:24 UTC (History)
10 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Krinkle 2014-05-09 14:37:19 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.

The initial portal wouldn't be unlike some of these:

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:
  ( * )

  Current solution: None

  Current workaround for regulars:

- Where would I find out about xml dumps?

  Current solution: None

  Current workaround for regulars:

- Where would I find out about pageview count data?

  Current solution: None

  Current workaround for regulars:

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 for now, ultimately linking back to{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 and api.php/help
        exclusively, we should get API and Hooks documentation onto as well.

  - 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?
  ( * )
  * "See also: Wikidata"

* Communications
  - (e.g. link to tech blog, as currently linked from
  - mailing lists
Comment 1 Krinkle 2014-05-09 14:42:54 UTC
I think all of can migrate to appropriate paths on this domain.

Comment 2 Moiz Syed 2014-05-09 14:44:40 UTC
I'm in full support of this. 

As someone working on this, I would like this very much.
Comment 3 Krinkle 2014-05-09 15:04:46 UTC
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
 - 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).
Comment 4 Quim Gil 2014-05-09 16:44:02 UTC
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
Comment 5 Krinkle 2014-05-24 21:46:30 UTC
(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
 as well. To be documented at
Comment 6 Bawolff (Brian Wolff) 2014-05-24 21:51:12 UTC
Why not just have redirect to a page on That way people can update it as appropriate easily.

>- Where do I find out about the existence of:
>  *

Not much point telling people about the existence of a service they are not allowed access to.
Comment 8 Quim Gil 2014-08-26 06:54:57 UTC
Let's merge this discussion with the work done at Sorry for the duplicity of spaces, which will go away when we merge Bugzilla with Phabricator.

We have settled on -- see 

Name for the 'developer hub' 


URL of the Developer Hub

(In reply to Bawolff (Brian Wolff) from comment #6)
> Why not just have redirect to a page on
> 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

How to redirect from
Comment 9 Sumana Harihareswara 2014-09-23 19:53:45 UTC
Removing myself from cc on this as I prepare to leave Wikimedia Foundation.

Note You need to log in before you can comment on or make changes to this bug.