Core Platform Team/PET Work Processes/PET Workboards

Core Platform Team Workboards
The Core Platform Team maintains two essential workboards that support its work process and capture the current state of its work: The Core Platform Team board and The CPT Subteam Workboards. The first represents an external interface for other teams and individuals to pass tasks to the CPT via the tag #core-platform-team. The second is a collection of internally focused boards that are used for sprint management by CPT subteams.

Additionally, there are a set of associated Phabricator Workboards, Projects and tags for which the CPT is responsible. We are currently working to integrate these boards into our work process to ensure that tasks captured within them are covered by our CPT Task Triage process.

Core Platform Team(CPT)
This board contains the Team Inbox, Icebox and all of the Epics owned by CPT. It is an external facing board which provides other teams and individuals with a direct interface to the CPT work process.

Structure of CPT Workboard

 * Inbox column  This column is the entry point for tasks which are sent to the CPT by external teams and volunteers. The inbound tasks are then handled by the CPT Task Triage process, prioritised and appropriately assigned
 * Icebox  This is a long term storage for tasks that the CPT does not intend to work on. The tasks are kept as they provide context, information or technical discussion that may in form future work.
 * Initiative columns  These columns represent the Initiative undertaken by the CPT, they contain all Epics and tasks that describe the complete set of work required in order to complete an Initiative. These columns map directly to the CPT Initiatives.

CPT Workboards
This is the parent board for our team process, it contains the following


 * Inbox column
 * Product subteam 1's board
 * Product subteam 2's board
 * Clinic Duty Team’s board
 * Contractors’ board

Structure of Team Workboards
Columns:


 * User Story Backlog User Stories waiting to be converted to Engineering Tasks for a sprint
 * Next Sprint Tasks for next sprint
 * Create Engineering Task convert a User Story into Engineering Tasks that describes concrete pieces of work to be done
 * Estimate estimation is done as a group activity at Sprint Kickoff
 * Ready  Tasks for current sprint
 * Doing  Tasks being worked on actively
 * Add Testing Criteria add clear list of criteria to confirm functionality of task
 * Waiting for Review This is a list of tasks that anyone can pick up for review
 * Blocked Externally  This column should be watched and addressed by EM/PM
 * Product Acceptance Product Manager responsible for accepting
 * Ready to Deploy  Completed and Accepted by Product Manager, ready to move to the deploy process

Associated Projects, Tags and Workboards
There are a large number of code bases, projects, tags and workboards that the CPT is responsible for tracking and triaging. Some are directly linked to the CPT via Maintainers List and some are indirectly linked through association via Phabricator Projects, tags and workboards.

Maintainer Status Projects
This list is copied from the Maintainers List, it is not automatically updated.

Phabricator Projects and Workboards

 * MediaWiki-API
 * MediaWiki-Authentication-and-authorization
 * MediaWiki-Cache
 * MediaWiki-ContentHandler
 * MediaWiki-Database
 * MediaWiki-Page-protection
 * MediaWiki-User-login-and-signup
 * WMF-JobQueue
 * MediaWiki-JobQueue
 * PoolCounter
 * MediaWiki-Installer
 * Wikimedia-log-errors
 * MediaWiki-extensions-Scribunto

Boards we track but do not own exclusively


 * MediaWiki-General-or-Unknown

Phabricator Tags

 * Wikimedia-production-error

Integration of Existing boards/tags/projects

 * How do we move tasks across columns without generating notifications?
 * We can add herald rule to add CPT tag to new tasks?
 * How can we integrate MediaWiki-API into Clinic Duty?
 * Needs details or plan, needs code
 * Are there tasks on the MediaWiki-API board that CPT should be responsible for?
 * Yes -> Needs details or plan, needs code, needs review, in dev
 * Are there any tasks in-dev/needs review column that requires work?
 * Yes
 * Would it be useful to use time from Clinic Duty to surface tasks or should we assume that they will surface if needed?
 * Yes :)
 * Next steps:
 * Create herald rule to take CPT when it receives the tag for the first time -> Separate inbox for autotagged things
 * Can we use trigger or global herald rules?
 * Progressively include tasks into Clinic Duty