- Python 72.1%
- HTML 27.7%
- Shell 0.2%
Justin Wheeler
b40da20f58
This file provides operational context for AI coding agents (e.g., Claude, Codex, Gemini CLI, etc.) that interact with the Community Ops issue tracker. It follows the AGENTS.md open format specification (https://agents.md/), now stewarded by the Agentic AI Foundation under the Linux Foundation. The file documents the key patterns and conventions an AI agent needs to work effectively here, distilled from an extended project management session that restructured the tracker's labels, migrated tickets to partner team trackers, and rewrote the README: - **Project overview**: what this repo is (an issue tracker, not a software project) and what it contains - **Forgejo API access**: base URL, auth, common endpoints, and the label ID gotcha that differs from GitHub/GitLab - **Label system**: the full org-level vs repo-level taxonomy, exclusivity rules, and the five `function/` work streams - **Milestones**: quarterly system and roll-forward convention - **Related trackers**: where to redirect requests that belong in FDWG, Matrix WG, Design, Mentored Projects, etc. - **Ticket migration protocol**: create first, comment, then close - **Writing and git conventions**: ventilated prose, gitmoji commit format, GPG/DCO signing, AI disclosure trailers - **Consent workflow**: always draft and get approval before posting - **Issue template mapping**: which labels each template auto-applies Assisted-by: Claude Opus 4.6 (1M context) Signed-off-by: Justin Wheeler <jwheel@redhat.com> |
||
|---|---|---|
| .forgejo/issue_template | ||
| data | ||
| email-templates | ||
| scripts | ||
| AGENTS.md | ||
| LICENSE.txt | ||
| README.md | ||
Community + Operations = CommOps
This repository is the issue tracker for the Fedora Community Operations Team. Use this tracker to file requests, report problems, or propose new work for the team.
Filing a ticket
Choose the template that best fits your request:
| Template | Use when… |
|---|---|
| General Ticket | You have a suggestion, idea, or task that doesn't fit another template |
| New Member Nomination | You want to nominate someone to join the Community Ops Team |
| Virtual Fedora Release Party | You are planning a global Virtual Fedora Release Party |
| Fedora Election Organizing | You are an election wrangler planning community engagement for a Fedora Elections cycle |
Not sure where to file?
Some types of requests are handled by other teams:
| If your request is about… | File it here instead |
|---|---|
| Data analysis, metrics, or community health analytics | FDWG Analysis Requests |
| Matrix governance, bots, or moderation | Matrix WG Tickets |
| Design assets, logos, or branding | Design Team Tickets |
| Fedora Magazine content | Magazine Tickets |
| Mentored Projects proposals (e.g., Outreachy, GSoC) | Mentored Projects Tickets |
Label hierarchy
Every issue in this tracker is labeled to indicate what kind of work it involves and how it should be triaged. Labels are organized into exclusive groups — an issue can have at most one label from each group.
Work stream (function/)
Each issue belongs to one of the team's five work streams:
| Label | Description |
|---|---|
function/events |
Event production, release parties, conferences, streaming, and video processing |
function/communications |
Community Blog, newsletters, outreach content, and community messaging |
function/docs |
Documentation site, playbooks, guides, and contributor reference materials |
function/onboarding |
Newcomer experience, mentoring, intern programs, and team growth |
function/operations |
Team governance, repo management, meeting logistics, and internal process |
A sixth label, function/analytics, is retained for analytics-adjacent work, but most data analysis work is now tracked in the Fedora Data Working Group.
Scope (scope/)
Describes what kind of request an issue represents:
| Label | Description |
|---|---|
scope/bug |
Something isn't working |
scope/improvement |
Something we are either repeating or improving |
scope/new |
A new task or project for the team |
Triage status (?/)
Indicates where an issue is in the triage process:
| Label | Description |
|---|---|
?/needs triage |
A maintainer is needed to review and categorize this issue |
?/needs reporter feedback |
Additional information from the reporter is needed to advance |
?/needs team vote |
A vote from Community Ops team members is required |
?/needs changes |
Needs changes or fixes before closing |
State (state/)
Marks the resolution state of an issue, typically applied when closing:
| Label | Description |
|---|---|
state/approved |
Approved by the Community Ops team |
state/blocked |
Cannot move forward due to external dependencies |
state/duplicate |
This issue already exists elsewhere |
state/invalid |
This doesn't seem right or is out of scope |
state/wontfix |
This will not be worked on |
Standalone labels
| Label | Description |
|---|---|
good first issue |
Good for newcomers looking to get involved |
help wanted |
Needs help or input from the wider Fedora community |
meeting topic request |
Flagged for discussion in the next scheduled team meeting |
Milestones
Work is organized into quarterly milestones, each covering a three-month interval aligned to the calendar year:
| Quarter | Months | Example |
|---|---|---|
| Q1 | January – March | 2026 Q1 Team Goals |
| Q2 | April – June | 2026 Q2 Team Goals |
| Q3 | July – September | 2026 Q3 Team Goals |
| Q4 | October – December | 2026 Q4 Team Goals |
The milestone due date is the last day of the quarter. Issues that are not completed by the milestone due date are rolled forward to the next quarter. Not every issue requires a milestone — backlog issues and exploratory ideas may remain without a milestone until they are prioritized.
Getting involved
Want to contribute? Look for open issues marked good first issue or help wanted.
Read the getting started guide for new contributors. If you are not sure where to start, ask on the Discussion forum or in the Matrix room.
As our team is mostly volunteers, we may not notice new issues immediately. Thanks for your patience!