council/docs
council/docs
13
1
Fork 5
Code Issues 5 Pull requests 1 Projects Activity Actions
docs/council/modules/ROOT/pages/procedures/tickets.adoc
Justin W. Flory (he/him) de0d38c5a7
 Docs: Convert all docs to native AsciiDoc 
This commit is a significant refactor of all the Fedora Council
documentation into full, native AsciiDoc. This includes following
conventions commonly associated with AsciiDoc, such as the one sentence
per line convention and using more internal `xref` links across pages.
It also introduces explicit link anchors on all headings.

This commit is mostly invisible to the reader. All lines across the
Antora component are now written on one sentence per line, as per the
standard AsciiDoc convention. Following this convention makes future git
diffs easier to read when it comes to actual changes in meaning.

Additionally, where applicable, I updated names and titles of roles that
have since been changed, e.g. "Fedora Community Action & Impact
Coordinator" to "Fedora Community Architect".

Signed-off-by: Justin W. Flory (he/him) <jwf@redhat.com>
2023-10-19 23:28:55 -04:00

2.2 KiB
Raw Permalink Blame History

{team_name} ticket queue

The {team_name} uses a 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 #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 Code of Conduct issue tracker.

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.

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

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 elsewhere.