Page MenuHomePhabricator
Create Task
Maniphest T116025

Goal: Align Community Liaison and Developer Relations project management practices
Closed, ResolvedPublic
Actions

Description

This goal was initially planned as "Plan for adoption of Phabricator across WMF Community Engagement teams". However, that is a big bite, I have other big bites to solve this quarter, and it looks like it is being a busy quarter.

Community Liaisons and Developer Relations already share some processes, we both use Phabricator although at different degrees, and ultimately we both need to make happy the same WMF processes and some overlapping areas of our communities.

We don't need to have identical processes. For instance, CL deals with more sensitive information than DevRel, and are a lot more plugged into WMF Engineering projects.

Measurements of success coming soon.

Related Objects
Search...

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.
StatusSubtypeAssignedTask
· · ·
DuplicateQgilT125545 Phabricator Q&A session for Community Liaisons
ResolvedQgilT116025 Goal: Align Community Liaison and Developer Relations project management practices
ResolvedQgilT114137 Document how the Developer Relations team works
ResolvedQgilT119387 Community Liaison and Developer Relation quarterly goals for January - March 2016
· · ·

Event Timeline

Qgil created this task.Oct 20 2015, 3:46 PM
Qgil claimed this task.
Qgil raised the priority of this task from to Medium.
Qgil updated the task description. (Show Details)
Qgil added projects: Developer-Advocacy, DevRel-October-2015, Community-Relations-Support, DevRel-November-2015.
Qgil subscribed.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 20 2015, 3:46 PM
Qgil mentioned this in T109829: Developer Relations quarterly goals for October-December 2015.Oct 20 2015, 3:48 PM
Qgil renamed this task from Goal: Align Community Liaisons and Developer Relations project management practices to Goal: Align Community Liaison and Developer Relations project management practices.Oct 20 2015, 3:56 PM
Qgil set Security to None.
Qgil added a subtask: T114137: Document how the Developer Relations team works.
Qgil moved this task from To triage to October - December 2015 on the Developer-Advocacy board.Oct 27 2015, 7:11 PM
Qgil added a project: DevRel-December-2015.Nov 30 2015, 7:28 PM
Qgil added a subscriber: • Rdicerb.Dec 1 2015, 10:01 AM

Alignment at the quarterly goals level is happening via T119387: Community Liaison and Developer Relation quarterly goals for January - March 2016 and T114137#1831097.

The next steps are workboard and tasks. I have started to look at the Community-Relations-Support workboard, while casually looking at candidates for goals and while trying to organize tasks related to the WMF product development process (now also under #wmf-product-strategy). I have suggested some blocked/blocked-by relationships, I have asked about some tasks with descriptions unclear for outsiders, also about potential duplicated / completed / stalled tasks... Needless to say, I'm not intending to do this on a regular basis. Just trying to show by doing to @Rdicerb and the liaisons.

As soon as the quarterly goals planning is over, I want to document how DevRel works on workboards and tasks, to check what would make sense to be adopted by CL, and what can be improved based on their feedback.

Qgil moved this task from Backlog to Doing on the DevRel-December-2015 board.Dec 3 2015, 12:33 PM
Qgil mentioned this in T121555: Create a Collaboration-Community-Engagement project.Dec 16 2015, 10:07 AM
Qgil added a project: DevRel-January-2016.Jan 12 2016, 1:38 AM
Qgil moved this task from Backlog to Doing on the DevRel-January-2016 board.Jan 12 2016, 1:50 AM
Qgil added subscribers: Johan, Keegan, Quiddity and 4 others.Jan 12 2016, 2:27 AM

I think it is time to align at the Phabricator level. What about this:

  1. All liaisons would have a list of tasks assigned to them reflecting at least their non-core work (tasks with a clear completion, as opposed to regular processes and routines) and their current priority.
  2. The Community-Relations-Support team would start using monthly sprints starting with #Liaison-January-2016. We would use the same columns as in DevRel-January-2016, although feedback for improvement is welcomed. During January the goal is simply to tag the tasks that liaisons are currently working on. We would start reflecting monthly planning in February.
  3. The Community-Relations-Support workboard would be organized like the Developer-Advocacy workboard, including a column for team radar and then columns for each quarter.
Qgil moved this task from October - December 2015 to January-March 2016 on the Developer-Advocacy board.Jan 12 2016, 7:15 AM
Qgil moved this task from Backlog to January-March 2016 on the Community-Relations-Support board.Jan 13 2016, 1:20 AM
Qgil added a comment.Jan 13 2016, 1:30 AM

We discuss the proposal above at the Community-Relations-Support meeting today, and we agreed to try this out.

Qgil added a project: Liaisons-January-2016.Jan 13 2016, 1:31 AM
Qgil raised the priority of this task from Medium to High.Jan 14 2016, 3:35 AM

To-Do column in Community-Relations-Support workboard is now gone.

Kudos to @Quiddity for being the first liaison adding the Liaisons-January-2016 label to a task. :)

Qgil moved this task from Backlog to Doing on the Liaisons-January-2016 board.Jan 16 2016, 7:47 PM
Qgil added projects: DevRel-February-2016, Liaisons-February-2016.Jan 27 2016, 6:46 AM
Qgil moved this task from Backlog to Doing on the Liaisons-February-2016 board.Feb 2 2016, 1:47 PM
Qgil mentioned this in T125545: Phabricator Q&A session for Community Liaisons.Feb 2 2016, 6:04 PM
Qgil added a parent task: T125545: Phabricator Q&A session for Community Liaisons.
Qgil added a comment.Feb 10 2016, 1:31 PM

Under the Technical Collaboration umbrella, today the Community-Relations-Support and Developer-Advocacy share a way of working based on individual and team quarterly goals, both manage team and monthly sprint workboards, and both share a weekly meeting.

We will keep fine tuning as we go, but for now this is good enough to resolve this task.

Qgil closed this task as Resolved.Feb 10 2016, 1:31 PM
Qgil closed subtask T114137: Document how the Developer Relations team works as Resolved.Feb 11 2016, 11:20 AM
Qgil closed subtask T119387: Community Liaison and Developer Relation quarterly goals for January - March 2016 as Resolved.Apr 15 2016, 5:29 AM
• Phabricator_maintenance added a project: Goal.Aug 13 2016, 8:39 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