From 8995cc68c62bc4a7acca32aada8619b3a8238914 Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Aug 26 2020 19:12:54 +0000 Subject: Add documentation on how we use tickets I would like to bulldoze this and start over, but for now let's at least document the current state. --- diff --git a/council/modules/ROOT/pages/procedures/tickets.adoc b/council/modules/ROOT/pages/procedures/tickets.adoc new file mode 100644 index 0000000..5a19e5b --- /dev/null +++ b/council/modules/ROOT/pages/procedures/tickets.adoc @@ -0,0 +1,44 @@ += Council ticket queue + +The Fedora Council uses a https://pagure.io/Fedora-Council/tickets/issues[ticket queue] to track decisions and other work. +When opening a ticket to request a decision from the Council, please describe the issue in detail but have an explicit question (or better, a proposal) to decide on. +If you are looking to start a discussion, consider posting to the https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/[council-discuss mailing list] first. + +NOTE: Do not file Code of Conduct reports in the Council issue tracker. Those should be filed against the https://pagure.io/coc/issues[Code of Conduct] issue tracker. + +== Issue priorities + +Currently, the Council uses the following priorities for tickets: + +* **OMG Urgent!!!1**: The ticket should be acted on asynchronously as soon as possible. +* **Needs Review** (default): The ticket needs to be triaged. +* **Next Meeting**: The ticket should be addressed in the next meeting. +* **Coming up**: The ticket is lower priority. +* **Waiting on {Assignee, Reporter, External}**: The ticket is blocked on action or input from someone. + +== Issue tags + +The Council uses tags to indicate the topic of issues. +Mutliple tags should be applied when appropriate. + +* **budget**: Big-picture budget issues +* **code-of-conduct**: +* **documentation** +* **elections** +* **events** +* **hackfests** +* **mindshare**: Related to the Fedora Mindshare Committee +* **objectives** +* **policies** +* **spending-request**: For as-we-go allocations +* **ticket-vote**: Indicates an issue that should be voted on by Council members +* **trademarks** + +== Voting + +When a vote is called for, the **ticket-vote** tag should be applied. +Council members should vote by leaving a comment of +1 (in favor), 0 (abstain/no opinion/weakly opposed), or -1 (opposed). +If multiple proposals or multiple versions of a proposal have been made, please indicate which the vote applies to. +Council members can provide additional context explaining their vote, but should still indicate explictly which of +1, 0, or -1 applies. + +Policies for voting and approval are covered xref:index#_making_decisions[elsewhere].