docs/council/modules/ROOT/pages/procedures/tickets.adoc

include::ROOT:partial$attributes.adoc[]

= {team_name} ticket queue

The {team_name} uses a link:{team_issue_tracker}[ticket queue] to track decisions and other work.
When opening a ticket to request a decision from the {team_name}, 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 link:{team_asynch_communication}[#council tag on Fedora Discussion] first.

[IMPORTANT]
====
Do not file Code of Conduct reports in the {team_name} issue tracker.
Those should be filed against the https://pagure.io/CoC/issues[Code of Conduct] issue tracker.
====


[[priorities]]
== Issue priorities

Currently, the {team_name} 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.


[[tags]]
== Issue tags

The {team_name} uses tags to indicate the topic of issues.
Multiple 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 {team_name} members.
* *trademarks*:


[[voting]]
== Voting

When a vote is called for, the **ticket-vote** tag should be applied.
{team_name} 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.
{team_name} members can provide additional context explaining their vote, but should still indicate explicitly which of +1, 0, or -1 applies.

Policies for voting and approval are covered xref:index.adoc#decisions[elsewhere].