Page MenuHomePhabricator

Document how the Developer Relations team works
Closed, ResolvedPublic

Description

In one of the Developer-Advocacy meetings, it was said that our planning process should be documented for clarity. We have a roadmap, team and individual quarterly goals, a team project workboard, monthly sprints, columns in each of these workboards... It is actually simple... but maybe not always simple, and definitely not simple for a newcomer.

Event Timeline

Qgil claimed this task.
Qgil raised the priority of this task from to Medium.
Qgil updated the task description. (Show Details)
Qgil added a subscriber: Qgil.
Aklapper set Security to None.

Gave this a quick shot, see the task summary. Feel free to edit/adjust/ignore/copy.

Thank you! What a nice surprise. I will polish your text and paste it in our wiki page. However, reading this documentation helped me writing down an idea to simplify our roadmap that has been floating around in the past weeks: T101099#1690826

Qgil raised the priority of this task from Medium to High.Nov 3 2015, 4:41 PM

https://www.mediawiki.org/wiki/Developer_Relations/Planning#Roadmap drafted, welcoming review. I have added the two ToDo questions in our team meeting agenda, but feel free to comment here if you wish.

Qgil lowered the priority of this task from High to Medium.Nov 25 2015, 12:34 PM

I have documented the part related to quarterly goals, which was the urgent one (see T119387).

https://www.mediawiki.org/wiki/Developer_Relations/Planning#Quarterly_goals

I plan to finish the rest in December.

Qgil raised the priority of this task from Medium to High.Jan 12 2016, 1:35 AM

Answering the two ToDo items on-wiki:

We don't have a high level roadmap. Should we? The current roadmap is not providing a quick picture of our future work, or a clear priority of tasks.

No. If we want to target more future work, I'd rather advocate using the quarterly columns in https://phabricator.wikimedia.org/tag/developer-relations/. Or create a "Proposed: 2017" column and break it down into quarterly columns at some point later in 2016. Regarding priority, we could even use the sorting in columns and not drag cards to random places. :D

We should highlight here the goals/tasks directly connected with the WMF annual plan. Should we?

Add a subsection bullet list "Tasks related to the WMF Annual Plan" under https://www.mediawiki.org/wiki/Developer_Relations/Planning#Roadmap once T124019 is sorted out.

I've done anything else in https://www.mediawiki.org/w/index.php?title=Developer_Relations%2FPlanning&type=revision&diff=2045777&oldid=2022751

@Qgil: So I think we are pretty done here. If you agree, please add a ToDo item in T124019 (or T115345?) (list Annual Plan stuff under https://www.mediawiki.org/wiki/Developer_Relations/Planning#Roadmap ), remove the "ToDo" section and the Draft header on-wiki, and resolve this task. kthxbye. ;)

I also killed mw:Developer_Relations#Planning by linking to the /Planning subpage. It was just duplication and I dislike updating several places manually with the very same data.
Feel very free to revert me.

Oooh, thank you very much!

@Qgil: So I think we are pretty done here.

Agreed.

If you agree, please add a ToDo item in T124019 (or T115345?) (list Annual Plan stuff under https://www.mediawiki.org/wiki/Developer_Relations/Planning#Roadmap ), remove the "ToDo" section and the Draft header on-wiki, and resolve this task. kthxbye. ;)

What I will do instead is to consolidate all these team annual plans, goals, and processes under https://meta.wikimedia.org/wiki/Technical_Collaboration

Since the Developer Relations part is covered, I will resolve this task. Again, thank you very much.