From cb0a2e9ddd41e4b7115a260706b0e484013f4831 Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Dec 01 2021 16:37:54 +0000 Subject: Remove the Infra Priorities Board docs It never really took off and the Taiga instance is shutting down in ~2 weeks. --- diff --git a/council/modules/ROOT/nav.adoc b/council/modules/ROOT/nav.adoc index 009ad95..ffb9868 100644 --- a/council/modules/ROOT/nav.adoc +++ b/council/modules/ROOT/nav.adoc @@ -12,7 +12,6 @@ ** xref:policy/edition-promotion-policy.adoc[Edition Promotion Policy] ** xref:policies.adoc[Additional Policies] * Council Procedures -** xref:procedures/infra_priorities_board.adoc[Infrastructure Priorities Board] ** xref:procedures/team_directory.adoc[Team Directory] ** xref:procedures/tickets.adoc[Ticket Queue] * xref:history.adoc[Council and Board Historical Membership] diff --git a/council/modules/ROOT/pages/procedures/infra_priorities_board.adoc b/council/modules/ROOT/pages/procedures/infra_priorities_board.adoc deleted file mode 100644 index 2757adb..0000000 --- a/council/modules/ROOT/pages/procedures/infra_priorities_board.adoc +++ /dev/null @@ -1,35 +0,0 @@ -= 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.