Issue & PR Labels on Fedora Forge
The Fedora Mindshare Committee uses a shared set of labels across all repositories in the Fedora Forge "mindshare" organization. These labels are defined at the organization level and are inherited by every repository.
Labels that share a prefix (e.g., scope/) are exclusive: only one label from that group can be applied to an issue at a time.
This prevents conflicting states like an issue being both state/approved and state/blocked.
Charter area (charter/)
These labels identify which pillar of the Fedora Mindshare Committee charter an issue or pull request supports. Not every issue needs a charter label. Apply one when the issue targets how the Committee works on, plans, or budgets within a charter area. Individual event requests and funding proposals do not need a charter label.
| Label | Description |
|---|---|
|
Regional Event Support: process, planning, and budgeting for events |
|
Recognition Service: contributor recognition programs and awards |
|
Digital Ambassadorship: online community engagement and outreach |
Needs (needs/)
These labels indicate what an issue is waiting on before it can move forward.
| Label | Description |
|---|---|
|
An event request that needs a published event report before closing as complete |
|
Additional feedback or information from the reporter is needed to advance |
|
A vote is required from Fedora Mindshare Committee members in order to advance |
Scope (scope/)
These labels describe the nature of the request.
| Label | Description |
|---|---|
|
Something is not working |
|
Repeating or improving something that already exists |
|
Something brand new that has not been done before |
State (state/)
These labels track the current status of an issue.
| Label | Description |
|---|---|
|
Approved by the Fedora Mindshare Committee |
|
Cannot move forward: blocked by feedback, other tickets, or external dependencies |
|
This issue or pull request already exists |
|
This does not seem right |
|
This will not be worked on |
Team (team/)
These labels identify which Fedora team is most relevant to an issue.
| Label | Description |
|---|---|
|
Fedora Advocates |
|
Fedora Ambassadors |
|
Fedora Community Operations (CommOps) |
|
Fedora Council |
|
Fedora Design Team |
|
Fedora Documentation Team |
|
Fedora Globalization Team (Localization and Internationalization) |
|
Fedora Marketing Team |
|
Fedora Mindshare Committee itself |
|
Fedora Websites & Apps Team |
Other
These labels are not exclusive and can be combined with any of the above.
| Label | Description |
|---|---|
|
Good for newcomers who want to get involved |
|
Needs help or feedback from the wider Fedora community |
Want to help? Learn how to contribute to Fedora Docs ›