Page MenuHomePhabricator

Goal: Clarify community engagement in WMF product development process
Closed, DeclinedPublic

Description

This task is a Community-Relations-Support quarterly goal for January-March 2016.

The ultimate objective is to implement the precise steps of community involvement in the WMF Product Development Process - make sure they work and are followed. The first step (covered in this task) is to define how communities and development teams are expected to work together.

Measurement of success

  • Documented steps for engaging with communities in product stages - T126296
  • Proposal for product prioritization which includes communities

Related Objects

StatusAssignedTask
DuplicateQgil
ResolvedQgil
ResolvedQgil
DuplicateNone
DuplicateNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
DuplicateNone
ResolvedKeegan
OpenNone
InvalidKeegan
DeclinedKeegan
ResolvedKeegan
DeclinedNone
ResolvedKeegan
DeclinedNone
ResolvedMoushira
StalledNone
OpenNone
ResolvedQgil
ResolvedKeegan
ResolvedKeegan
OpenNone
ResolvedMoushira

Event Timeline

Qgil created this task.Jan 19 2016, 10:34 AM
Qgil updated the task description. (Show Details)
Qgil raised the priority of this task from to Normal.
Qgil added a subscriber: Qgil.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 19 2016, 10:34 AM

As a documentation starter:

The WMF product development process very much looks like a waterfall process or method. Is that intentional or inevatible? Isn't that at odds with agile / scrum software development?

The WMF product development process very much looks like a waterfall process or method. Is that intentional or inevatible? Isn't that at odds with agile / scrum software development?

Hi @AdHuikeshoven, as this task is about clarifying the community engagement in the process (emphasis by me), could you bring up your question on https://www.mediawiki.org/wiki/Talk:WMF_product_development_process ? Thanks a lot!

Qgil added a comment.Jan 20 2016, 2:52 PM

@AdHuikeshoven, see the long discussion at https://www.mediawiki.org/wiki/Topic:Srnkvh5ip21d2mto

Bottom line: you can be as agile and as iterative as you want, but there is still one point where a concept starts becoming a plan, a point where a plan starts having a design, a point where a project gets more resources, a point where a functional prototype can be tested, etc.

Keegan claimed this task.Jan 20 2016, 9:08 PM
Keegan set Security to None.
Keegan added a comment.Feb 4 2016, 8:06 PM

Very initial pen-to-paper-to-wiki page beginning: https://www.mediawiki.org/wiki/User:Keegan_(WMF)/sandbox2

Elitre added a subscriber: Elitre.Feb 9 2016, 6:39 PM
Qgil added a comment.Apr 6 2016, 1:23 PM

@Keegan , this task was one of the T119387: Community Liaison and Developer Relation quarterly goals for January - March 2016. For the current quarter we have T131883: Communication workflows between WMF Product teams and Wikimedia communities. Should we keep this task open and continue working on its blockers from here, or should we "dissolve" the missed goal and work directly on these tasks?

Keegan closed this task as Declined.Jun 14 2016, 1:37 AM

@Keegan , this task was one of the T119387: Community Liaison and Developer Relation quarterly goals for January - March 2016. For the current quarter we have T131883: Communication workflows between WMF Product teams and Wikimedia communities. Should we keep this task open and continue working on its blockers from here, or should we "dissolve" the missed goal and work directly on these tasks?

Dissolving this, yes. It became other tasks.