This tag has been archived. Please use Web-Team ( https://phabricator.wikimedia.org/project/view/7529/ ) instead
Description before being archived
Hey there!
We need your help making the software that powers Wikipedia even better.
Feel free to comment on any of the tasks you see and ask if you can help with anything that looks interesting.
Wikimedia sites are kept up and running by a small group of staff from the Wikimedia Foundation and volunteers like yourself.
This Web-Team-Backlog is used to focus engineering efforts around the reading (including Extension:MobileFrontend) web experience for the various WMF projects.
Before doing anything be sure to read all about our projects and then if you want to help us out in anyway you can...
- Sign up for a Phabricator account
- Head over to our irc channel on Libera.Chat (#wikimedia-mobile)
- Send an e-mail to our mailing list. You can maybe pitch an idea you have or simply say hi telling us: who you are, what your skillset/interest is & what you want to help us with. we will do our best to point you at other Phabricator tasks that you can help us with :-)
Here's how the team uses the workboard columns:
To Triage
This is where incoming tasks arrive on the board. Cards that have been reviewed by the team are removed from Triage and put in one of the following columns. If a card leaves Triage for any column but Tracking, it must be given a priority.
Needs Analysis
These are tasks that the team has triaged, but need further discussion before they can be queued for future work. This can include Design work or attention from devs or Product.
Triaged but Future
These tasks are ready to enter future sprints, although they may require review and estimation from the team before actual work begins.
Upcoming
These are the tasks that are tentatively scheduled for the sprint after the current. These tasks are moved to "Current Sprint (and resolved Q etc)" when the sprint starts.
Current Sprint (and resolved Q etc)
These are tasks that the team has completed this quarter (marked "Resolved"), as well as the tasks they are currently doing (any "Open" status).
Needs Reproduction
Tasks go here when the team would like QA to review tasks that have been filed but need verification before the tasks are actionable.
Epics
These tasks are large tasks with many subtasks. While the subtasks go through workflow, these cards remain static.
Product Owner Backlog
A place that the PO of the team can store tasks to which she needs to attend.
Design
This Milestone is for tracking work for which the Reading Web Team's designer is responsible. When something needs Design attention, it is pulled into this Milestone. When that attention has been completed, the task is removed from the Milestone and returned to the Web-Team-Backlog (not resolved).
Tracking
Tasks in this column are not usually worked on by the team. The tasks are those that other teams or volunteers are doing. This column also serves as a place for cards that are tagged on multiple teams, where the subtasks are completed by each team. This protocol prevents teams that are affected by similar issues, but require different solutions, from overriding one anothers' workflows (priority, story points, etc). This column is a Phabricator Milestone to take advantage of categorizing tasks into columns.
