Wikimedia Research/Research and Data/Phab Process

Research Phab Process

All tags listed here:

https://phabricator.wikimedia.org/project/profile/45/

Workboards:

Research and Data: https://phabricator.wikimedia.org/project/view/45/ Revscoring: https://phabricator.wikimedia.org/tag/revscoring/

Tags:

Research Collaboration: https://phabricator.wikimedia.org/project/view/1394/

Research Consulting: https://phabricator.wikimedia.org/project/view/1402/

Research Management: https://phabricator.wikimedia.org/project/view/1395/

Fundraising Research: https://phabricator.wikimedia.org/project/view/1390/

Contributor value research https://phabricator.wikimedia.org/tag/contributor_value_research/

Increasing content coverage https://phabricator.wikimedia.org/tag/increasing_content_coverage/

Improving access: https://phabricator.wikimedia.org/tag/improving_access/

Data release: https://phabricator.wikimedia.org/tag/data_release/

VisualEditor experimentation: https://phabricator.wikimedia.org/tag/visualeditor_experimentation/

Briefcase:

Research and Data archives: https://phabricator.wikimedia.org/project/view/1389/

Research Ideas: https://phabricator.wikimedia.org/tag/research_ideas/

Projects (with workboards) vs project tags

• In general, each task will have only 1 main project it belongs to from a workflow perspective and an arbitrary number of project tags that are used to categorize it. Project tags will not have corresponding boards. In some cases, a task might be co-owned by multiple projects that are not just tags: when that happens, one of these projects will be designated as the owner of the task.

Creating tags

• You usually should not worry about creating new tags. Dario, Abbey and Grace have privileges to create new projects/tags, but these should not change as they are linked to the Master Project List
• If you feel work you're doing is a significant deviation from the goals or the scope of a project, come and talk to us.

Creating tasks:

• Create tasks as granular as possible: the worst possible scenario is one in which an entire quarterly or annual goal is captured in a single task.
• Make sure the title and scope of the task are understandable and include links to external docs when appropriate
• Priority Each task will typically be created as "Needs Triage", the product owner will triage tasks and assign them a priority. In most cases this will be Dario or Abbey (an example of exception is Revscoring where Aaron is acting as owner for that team)
• Tag When you create a task, please add the most relevant project tag, if you don't know what that is, Dario or Abbey will take care of that

Updating tasks and changing their status

• We'll be reviewing the status of individual tasks during weekly Backlog grooming sessions.
• Please keep tasks up-to-date: posting a short update as a comment helps the rest of the team understand if a task is moving forward or is stuck
• When a task is completed, move it to the Done column without marking it as resolved, where the owner will review it and close it / archive it (i.e. move it to the archive board). The only exception is when the workflow for a task is handled via a different workboard, in which case it's the corresponding owner's responsibility to close it.
• If a task needs to be closed for any reason other than "resolved", go ahead and close it but please move it to the "done" column.
• The product owner will review tasks moved to "Done" and move them to the archive table: you shouldn't worry about moving tasks across boards, Archive is for reporting purposes only. Product Owner will mark tasks as Resolved on the Archive board