From 6ec1491aaf56dc25345213ada28d6fc33dca01ed Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Aug 25 2020 14:54:13 +0000 Subject: Add the first draft of guidance for using the infrastructure priorities board. This will probably need heavy refinement after getting some use, but it's a vast improvement over the existing documentation, which was: --- diff --git a/council/modules/ROOT/pages/procedures/infra_priorities_board.adoc b/council/modules/ROOT/pages/procedures/infra_priorities_board.adoc new file mode 100644 index 0000000..2757adb --- /dev/null +++ b/council/modules/ROOT/pages/procedures/infra_priorities_board.adoc @@ -0,0 +1,35 @@ += Infrastructure Priorities Board + +The Fedora Council maintains a https://teams.fedoraproject.org/project/fedora-council-infrastructure-priorities/kanban[Taiga board for tracking infrastructure projects]. +This is intended to provide a simple and public tracker of the high-level concepts of infrastructure projects sent to the Community Platform Engineering (CPE) team. + +== Access + +All current Fedora Council members have privileges on the board to create and modify user stories. +Community members who have suggestions may request access or ask a Council member to shepherd the suggestion. + +== Workflow + +Ideas for infrastructure projects to send to CPE should be created as a user story in the **Ideas** column. +It is not necessary at this point to have the concept fully-developed. +However, you should leave a sufficent level of description in the user story to explain what will be requested and why. +Links to existing content (issue trackers, Bugzilla, documentation, etc) are fine; it is not necessary to copy all supporting content. + +TIP: You are not obligated to take ownership of projects you suggest. +However, you also should not assume that others will take on unowned projects. + + +When someone is willing to take ownership of developing the idea into a more developed concept, the user story should be moved to the **Writing** column. +At this stage, the Council member tasked with this should set themselves as the assignee. +Write a requirements document (also called "epic brief") according to the https://docs.fedoraproject.org/en-US/cpe/initiatives/[requirements of the CPE team]. +When the requirements document is ready for discussion and review, add a link to the user story's **Requirements doc** field. + +Prior to CPE's https://docs.fedoraproject.org/en-US/cpe/time_tables/[quarterly planning meeting], the Council will discuss the ready projects and determine which ones to send to CPE. +Projects sent to CPE will be moved into the **Submitted to CPE** column. + +If a project is selected by CPE, it will be moved to the **In Progress** column. +Where available, links to CPE's Jira or Taiga instances should be added to the corresponding field on the user story. +When a project is completed, it will be moved to the **Done** column. + +Projects that are not selected or have stalled will remain until the next quarter. +Projects that are rejected or abandoned should have the user story deleted.