Page MenuHomePhabricator

Developer Relations Roadmap
Closed, ResolvedPublic


This roadmap an overview of the Developer-Advocacy team plans and assumptions. It is organized by US fiscal years (just like the rest of Wikimedia Foundation activities), and then by quarters. More details can be found in the team's workboard and in every monthly sprint.

July 2015 - June 2016

See also: meta:Wikimedia Foundation Annual Plan/2015-16

July - September 2015

  1. T101946: Goal: First Wikimania Hackathon fully integrated with the main program and the editor community
  2. T101441: Goal: Integrate the new Web APIs hub with
  3. T88531: Goal: Organize a Gerrit Cleanup Day on September 23, 2015
  4. T101393: Goal: All completed GSoC and Outreachy projects have code merged and deployed by September
  5. T101950: Goal: Establish a framework to engage with data engineers and open data organizations
  6. T104282: Goal: Create landing pages for the free open knowledge sources on the Web APIs Hub

See also

October - December 2015

See also:

January - March 2016

  • MediaWiki Developer Summit in San Francisco on 4-6 January
  • FOSDEM in Brussels on 30-31 Juanuary
  • Wikimedia-Hackathon-2016-Organization
  • Proposed: Clean our list of patches waiting for review in Gerrit
  • Proposed, if it makes sense in the context of T31923: Install Q&A system at
  • Proposed: integration of presentations recorded (events, Tech Talks...), slides, and other materials with
  • Organizing Google Summer of Code 2016 and Outreachy round 11 & 12

April - June 2016

  • Wikimedia-Hackathon-2016 in Jerusalem on 31 March - 4 April
  • Organizing Wikimania Hackathon 2016, held in Esino Larion on 22-24 June
  • Proposed: Wikimedia Foundation commits to a service-level agreement on code review for patches submitted to the repositories we maintain
  • Proposed: integration of and
  • Organizing Google Summer of Code 2016 and Outreachy round 12

July 2016 - June 2017

  • MediaWiki Developer Summit 2017
  • Wikimedia Hackathon 2017
  • Wikimania Hackathon 2017
  • Organizing Google Summer of Code 2016 & 2017 and Outreachy rounds 12 & 13 & 14
  • Organizing Google Code-in 2016

July 2017 - June 2018

  • MediaWiki Developer Summit 2018
  • Wikimedia Hackathon 2018
  • Wikimania Hackathon 2018
  • Organizing Google Summer of Code 2017 & 2018 and Outreachy rounds 14 & 15 & 16
  • Organizing Google Code-in 2017

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

Qgil claimed this task.
Qgil raised the priority of this task from to Medium.
Qgil updated the task description. (Show Details)
Qgil subscribed.

Yesterday @Spage asked whether this roadmap should be here in Phabricator or on-wiki. After thinking a bit more, it is probably easier to start here, in the description of this task. It's the simplest setup, it already implies having to sync once between the content of this roadmap and the quarterly goals, but just once. If we just to on-wiki already, we will need to keep an additional place in sync.

Since this is an experiment, let's start here and we'll see. Agreed?

Qgil set Security to None.
Qgil lowered the priority of this task from Medium to Low.Jun 28 2015, 8:55 AM

I think this roadmap is ready as far as it gets for the ECT-June-2015 objective. If you have urgent ideas for it, please bring them on. Otherwise let's chage to work-in-progress mode.

The #engineering-community workboard was suboptimal, with columns redundant to the monthly sprints. Now I have added columns for each quarter, as a way to help visualizing the roadmap there.

Let's see how it goes. Keeping it up to date requires certain redundancy, and there is a risk of having things out of sync. The benefit is that tasks planned for a quarter will show the little piece of info in their headers.

Qgil renamed this task from Engineering Community Roadmap to Developer Relations Roadmap.Sep 13 2015, 12:35 PM
Qgil updated the task description. (Show Details)

I'm thinking that keeping this Roadmap task brings manual overhead and a remarkable amount of duplication with the Developer-Advocacy workboard, which is now organized by quarters and I find that very practical.

What should be done to deprecate this roadmap task and rely only on the workboard:

  • Create new tasks for events that we are expecting, even if they are far away, i.e. "Organize Wikimania Hackathon 2016".
  • Prioritize better the tasks in the current and the following quarter, because in these columns it is difficult to see what is more important. The rest of quarters in the more distant future have just a few tasks, so this is not a problem.

@Aklapper @Rfarrand @Spage what do you think?

Yes please. If we can turn every item into a dedicated task but I think we can.
There is the "Backlog" column for far away stuff, and if we wanted we could also have a far-away non-quarterly columns like "year 2017" as we can always hide columns when breaking stuff down into quarters as 2017 approaches.

This road-map task is being closed in favor of the Developer-Advocacy workboard and

The only relevant items without a task are:

Proposed: If nobody has committed to organize a community backlog, then we should step in (in the context of T78639)

This task will be lead by Community-Tech -- see T114193: Administer 2015 Community Wishlist Survey (tracking) and followup.

integration of presentations recorded (events, Tech Talks...), slides, and other materials with Web-APIs-Hub

I have added a point in the agenda of the DevRel weekly meeting to discuss what to do with this idea.

All the rest either has a task or is a predictable event. Closing, and thank you for your attention. :)