Page MenuHomePhabricator

Goal: Drive more complex long-term tasks closer to resolution
Closed, DeclinedPublic

Description

More complex tasks which involve several teams/areas and agreement on the way forward sometimes gain momentum but often momentum gets lost again.

Currently as a bugwrangler I don't have a very convincing concept to keep long-term tasks on my radar and help getting them done. I ping occasionally, but that's it.

I'd like to try keeping such tasks more on my radar, picking a limited number, and working with teams, developers, product managers to get such tasks closer and faster to resolution.

In Q3/2015, I'd like to try assigning three technical tasks to myself and driving them to resolution by gettting stakeholders involved and keeping them constantly on my radar.
This obviously requires commitment from the various stakeholders too.
If this works out I'll document good and bad experience and invite others to follow that path.

Tasks to try with:

Needs/welcomes syncing with German-Community-Wishlist and Community-Tech.

Event Timeline

Aklapper claimed this task.
Aklapper raised the priority of this task from to Low.
Aklapper updated the task description. (Show Details)
Aklapper added a subscriber: Aklapper.
Qgil moved this task from To triage to July-September 2015 on the Developer-Advocacy board.
Qgil added a subscriber: Qgil.
Aklapper updated the task description. (Show Details)Jun 29 2015, 3:27 PM
Aklapper set Security to None.
Aklapper added a project: ECT-August-2015.
Aklapper renamed this task from Start driving more complex long-term tasks closer to resolution to Goal: Start driving more complex long-term tasks closer to resolution.Jun 30 2015, 4:45 PM
Aklapper renamed this task from Goal: Start driving more complex long-term tasks closer to resolution to Goal: Drive more complex long-term tasks closer to resolution.Jul 6 2015, 1:00 PM
Aklapper updated the task description. (Show Details)
Aklapper lowered the priority of this task from Low to Lowest.EditedAug 3 2015, 8:02 PM

I'm personally putting the "Driving" part on the backburner because I'd first like to evaluate the approaches of Community-Tech who are working on T105942: Come up with potential criteria for scoring project/task ideas / T107833: Build an initial work backlog for Community Tech based on one or more existing community wishlists and getting some input from WMDE's TCB-Team based on https://de.wikipedia.org/wiki/Wikipedia:Technische_W%C3%BCnsche (currently being translated to English).
I'm happy to help (and I do, e.g. by going through the translation with BMueller) but there should not be three parties trying to achieve the very same goals (which wasn't foreseeable when I created this task in the middle of June).

Aklapper closed this task as Declined.Aug 25 2015, 4:23 PM

Per my last comment, I'm declining this task as the situation has changed a lot since I created this task - we now have two teams dedicated to driving popular outstanding long-term tasks to resolution.

Obviously I'm always around for these teams to provide help (I've had conversations with folks involved in/with both teams plus commented on some of their tasks), support and input. I'm also glad that these teams have development/engineering resources.