If http://juliuszgonera.com/wddh/ is intended to be THE prototype, then this task is basically completed. If not, then please explain and setup the actual prototype in order to work on it.
Description
Description
Details
Details
- Reference
- fl482
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Do not offer Project Tags to be added to Subscribers fields | repos/phabricator/phabricator!9 | aklapper | T303829 | wmf/stable |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Spage | T307 Announcing the Developer Hub prototype release | |||
| Resolved | • Spage | T299 Release the Developer Hub prototype | |||
| Declined | Qgil | T303 Setup the Developer Hub prototype |
Event Timeline
Comment Actions
qgil wrote on 2014-07-22 13:47:56 (UTC)
I wonder whether we should require to have the prototype hosted in Labs. Better than a personal host, isn't it? No strong opinion, though.
Comment Actions
jgonera wrote on 2014-07-22 22:41:15 (UTC)
It's hosted using GitHub pages now. No strong feelings about it though. I think we agreed on adding some real content to the prototype to call it finished.
Comment Actions
qgil wrote on 2014-08-25 12:25:38 (UTC)
@MSyed says: "I've forked Juliusz's repo on github and will be committing code here: https://github.com/moizsyed/build.wikimedia.org "
Comment Actions
According to T312, the hub is going to be a namespace in mediawiki.org with an own skin. In this case, the prototype... could be the real thing just in an official Work In Progress, right?
I don't see the point of sttarting some Labs instance when we can use mediawiki.org directly. Thoughts?
Comment Actions
@Spage is focusing on prototyping through the creation of actual content in mediawiki.org, under the API: namespace. From there we can decide what's next. In any case, prototyping using an external tool is currently out of scope. Therefore, I'm declining this task.