iBet uBet web content aggregator. Adding the entire web to your favor.
iBet uBet web content aggregator. Adding the entire web to your favor.



Link to original content: http://phabricator.wikimedia.org/T307
⚓ T307 Announcing the Developer Hub prototype release
Page MenuHomePhabricator
Create Task
Maniphest T307

Announcing the Developer Hub prototype release
Closed, ResolvedPublic
Actions

Description

The Developer Hub prototype release is a relevant event for our developer community and also for the purpose of developer outreach. We should have an announcement coordinated with Comms.

See it at http://devhub.wmflabs.org/wiki/Dev:Data_and_developer_hub , create blockers of this task or comment on related tasks TXX

Details

Reference
fl486

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedVolker_ET111117 [EPIC] Enhance accessibility of OOUI & MediaWiki UI library / LSG / MediaWiki General to screen readers and color-deficient users
 ResolvedNoneT88023 Create landmarks for screen reader
 DeclinedNoneT103986 issues with Data and Developer Hub prototype (tracking)
 DeclinedNoneT110835 `blueprint-left-nav` message doesn't seem to be localizable
 ResolvedQgilT101099 Developer Relations Roadmap
 ResolvedQgilT113030 Developer Relations quarterly review Jul-Sep 2015
 ResolvedQgilT101100 Engineering Community quarterly goals for July-September 2015
 Resolved• SpageT101441 Goal: Integrate the new Web APIs hub with mediawiki.org
 Resolved• SpageT307 Announcing the Developer Hub prototype release
 Resolved• SpageT299 Release the Developer Hub prototype
 Resolved• SpageT306 Featuring the first three APIs in the Developer Hub
 DeclinedNoneT335 Document the Content API in the Developer Hub
 ResolvedoriT334 Document RCStream in the Developer Hub
 DeclinedNoneT302 API sandboxes for the Developer Hub
 ResolvedNoneT300 Select the three APIs featured at the Developer Hub prototype
 DeclinedNoneT88755 Improve MediaWiki API example behavior
 ResolvedAnomieT89229 API Help should generate [try in ApiSandbox] link to Special:ApiSandbox#action=params from getExamples()
 OpenNoneT89318 Replace on-wiki API documentation with Special:ApiHelp transclusion
 OpenNoneT89768 Language support in Special:ApiHelp and its transclusion.
 OpenNoneT90528 Generated API Help doesn't indicate the MediaWiki versions that support a module and parameters.
 Resolved• SpageT89680 Template:ApiEx on mw.org should have a link to "[view in ApiSandbox]".
 ResolvedjeropbrendaT359 Document the Wikidata API in the Developer Hub
 OpenNoneT89863 [Task] Merge on-wiki Wikibase/API documentation into Wikibase apihelp strings.
 DeclinedQgilT303 Setup the Developer Hub prototype
 Resolved• SpageT305 Developer Hub homepage
 Resolved• SpageT301 Define the look&feel of the Developer Hub
 DeclinedNoneT93062 Define the navigation elements of the Web APIs hub
 DeclinedNoneT93613 Deploy Blueprint on mediawiki.org as optional and experimental skin
 Resolved• PrtksxnaT99757 Blueprint/LSG Table of Contents should be configurable on-wiki, like MediaWiki:Sidebar
 Resolved• PrtksxnaT103784 The Blueprint sidebar on devhub prototype is missing Discussion link
 Resolved• PrtksxnaT104288 Blueprint skin has no footer or replacement (so no copyright)
 Resolved• SpageT104672 Convert Blueprint to core's HTML templating
 ResolvedJdlrobsonT97188 Mustache templates in core do not support partials (client side)
 ResolvedNoneT110988 Blueprint assumes personal_urls[0] contains username
 DeclinedNoneT104673 Remove Blueprint's use of bootstrap
 ResolvedNoneT107662 Add bootstrap source files with components currently in use at Blueprint
 ResolvedQgilT104694 Community support for deploying Blueprint in mediawiki.org as optional/experimental skin
 ResolvedVolker_ET109135 Change `#searchInput` to `type="search"` and add `<label>`.
 Resolved• violettoT112308 Blueprint should include skip-to-nav and skip-to-content links
 ResolvedVolker_ET119444 Integrate CSS mixin for screen reader and keyboard-only users into core
 ResolvedVolker_ET112342 Make Blueprint fully localizable
 DeclinedNoneT112487 Blueprint HTML output lacks headings (document) structure
 ResolvedNoneT110983 Blueprint sidebar reuses #firstHeading id
 ResolvedVolker_ET107213 Blueprint should make use of HTML5 <header> and <main> element with correct ARIA roles
 DeclinedNoneT113208 Consolidate CSS background images implementation with core mixins or ResourceLoaderImageModule
 ResolvedVolker_ET104213 No icon for "View source" and "Edit" in sidebar
 ResolvedVolker_ET113296 Keyboard selector (IMESelector) not correctly viewed on main search in Blueprint
 ResolvedVolker_ET107026 Cleanup `font` properties and let section edit link `.mw-editsection` use sans-serif font
ResolvedVolker_ET116722 Align Blueprint to Jenkins' composer.json validation
 ResolvedPastakhovT114463 Blueprint skin does not render all what it should
 ResolvedNoneT103452 Blueprint skin does not render page indicators
 ResolvedPastakhovT116130 "Undefined index: userpage" error when user is logged out
 ResolvedNoneT117843 The link of sidebar menu is directed to server root instead of wiki homepage
 ResolvedVolker_ET118113 Address FOUC of Toc in Blueprint
 ResolvedNoneT114212 Do not put the role="search" on the form element
 ResolvedVolker_ET121840 Remove obsolete LivingStyleGuide.php from Blueprint
 ResolvedVolker_ET122117 Bootstrap's CSS rule "box-sizing: border-box;" breaks VE toolbar
 ResolvedVolker_ET122753 Blueprint should use MediaWiki core's Less mixins
 DeclinedNoneT317 "Terms of Use" must be prominently featured in the Developer Hub
 Resolved• SpageT92941 Define personas for dev.wikimedia.org
 Resolved• SpageT92945 Reflect in dev.wikimedia.org what Wikimedia offers to developers
 Resolved• SpageT98164 prototype Data and developer hub with Blueprint skin

Event Timeline

• flimport raised the priority of this task from to Medium.Sep 12 2014, 1:43 AM
• flimport added a project: Web-APIs-Hub.
• flimport set Reference to fl486.
• flimport added a subscriber: Qgil.Oct 2 2014, 9:49 PM
• flimport added a subscriber: revi.Oct 10 2014, 9:00 PM
Qgil lowered the priority of this task from Medium to Low.Oct 22 2014, 6:20 PM
• Spage mentioned this in T299: Release the Developer Hub prototype.Mar 23 2015, 9:49 PM
• Spage removed a parent task: T299: Release the Developer Hub prototype.Mar 23 2015, 10:39 PM
• Spage mentioned this in T372: Redirect dev.wikimedia.org to mediawiki.org.Mar 24 2015, 1:51 AM
Qgil mentioned this in T93770: Engineering Community quarterly goals for April-June 2015.Mar 24 2015, 5:00 PM
• Spage added a subtask: T299: Release the Developer Hub prototype.Mar 24 2015, 5:32 PM
• gpaumier added projects: Developer-notice, User-notice.Mar 24 2015, 5:33 PM
• gpaumier set Security to None.
• gpaumier moved this task from To Triage to Not ready to announce on the User-notice board.
• Spage closed subtask T299: Release the Developer Hub prototype as Resolved.Jun 2 2015, 10:21 AM
• Spage added a project: ECT-June-2015.Jun 2 2015, 10:27 AM
• Spage added subscribers: • MSyed, • Spage.

This should be doable after some polishing based on feedback from @Qgil, @MSyed, etc.

• Spage claimed this task.Jun 2 2015, 5:20 PM
• Spage updated the task description. (Show Details)
• Spage mentioned this in T101100: Engineering Community quarterly goals for July-September 2015.Jun 4 2015, 6:27 PM
• Spage mentioned this in T101441: Goal: Integrate the new Web APIs hub with mediawiki.org.Jun 4 2015, 8:44 PM
Qgil added a subtask: T305: Developer Hub homepage.Jun 15 2015, 9:34 PM
• Spage raised the priority of this task from Low to High.Jun 16 2015, 4:10 PM

Announce soon

• Spage moved this task from Backlog to Doing on the ECT-June-2015 board.Jun 16 2015, 4:11 PM
• Spage added a subtask: T103049: Enable Flow on Web APIs talk pages on mediawiki.org.Jun 19 2015, 3:16 AM
Qgil mentioned this in T103049: Enable Flow on Web APIs talk pages on mediawiki.org.Jun 19 2015, 8:44 AM
Qgil removed a subtask: T103049: Enable Flow on Web APIs talk pages on mediawiki.org.
Qgil added a comment.Jun 19 2015, 8:47 AM

I removed T103049 as blocker. I agree that Flow in discussion pages is a must, but if you want Flow by the announcement of the prototype, it needs to be enabled IN the prototype. :)

Before doing that, we need to make sure that we will be able to migrate those discussion pages (just like we will need to migrate the content pages themselves).

Qgil mentioned this in T369: Implement a namespace in mediawiki.org to host the developer hub.Jun 24 2015, 8:38 PM
• Spage added a comment.Jun 25 2015, 6:11 AM

@Qgil, P840 is draft announcement for wikitech-l and engineering lists.

Qgil added a comment.Jun 25 2015, 6:40 AM

Ok, this is a very good start. Just a few comments:

  • https://www.mediawiki.org/wiki/dev.wikimedia.org should be presented as the main project page, and its discussion page as the main channel for general feedback. Commenting on existing tasks and creating new tasks should be presented as the preferred channel for specific feedback. Reply to this thread should be the last option, for lazy brats.
  • "Around the 2014 Zurich Hackathon" should say "Since December 2013". I would say "Moiz Syed and others" since he has been the only clear driver still around, also not to get into too much details of by Juliusz and not Stephen, etc.
  • You might want to mention explicitly that the master versions of the pages are in mediawiki.org, and that they are imported from time to time to the prototype. I didn't know that and I'm watching this project, so I guess the rest will not know either.
  • The FAQ is the best and most hilarious FAQ I have read for a long time. Thank you for this. The only change I would make is remove "Prateek Saxena, Andrew Garrett, and May Galloway" and add "The Design team (now Reading Design)". Again, not to dwell too much into genealogy, which makes this announcement look like targeted to a small audience of insiders instead of our tech community at large and beyond.

Also, why bother so much about the format? This is an announcement to be sent primarily via email, right?

• Spage closed this task as Resolved.Jun 26 2015, 3:35 AM

Announced!

In T307#1399157, @Qgil wrote:

Also, why bother so much about the format? This is an announcement to be sent primarily via email, right?

I forgot that wikitech e-mail is ASCII-only :-) But it still saves me time when composing to have Phabricator auto-link tasks.

Qgil added a comment.Jun 26 2015, 4:07 AM

Congratulations! Phew.

We might want to recycle the FAQ in the wiki page, as a way to direct
people asking or mentioning topics covered there.

• gpaumier moved this task from Not ready to announce to Announce in next Tech/News on the User-notice board.Jun 26 2015, 9:19 PM
• gpaumier moved this task from Announce in next Tech/News to In current Tech/News draft on the User-notice board.
• gpaumier moved this task from In current Tech/News draft to Recently announced in Tech/News on the User-notice board.
• gpaumier moved this task from Recently announced in Tech/News to Already announced/Archive on the User-notice board.Jul 3 2015, 11:41 PM
• Spage closed subtask T305: Developer Hub homepage as Resolved.Jul 28 2015, 5:23 AM
Krinkle moved this task from Backlog to Archive on the Developer-notice board.Apr 18 2016, 9:16 PM
Ladsgroup edited projects, added User-notice-archive; removed User-notice.Aug 13 2022, 1:54 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits