The Fedora Council uses this to record ongoing work and to track issues which need a specific resolution.
https://docs.fedoraproject.org/en-US/council/
Establish `AGENTS.md` following the convention used across a few Fedora Forge repos (`commops/tickets`, `council/flock`, `marketing/tickets`, etc.) to provide AI coding agents with the context needed to interact with the Council's issue tracker via the Forgejo REST API. The file documents the repository structure, issue template conventions (Summary-Background-Details-Outcome format), the complete label taxonomy (org-level triage/role/scope/state labels and repo-level category labels), milestone conventions, related Council trackers, Forgejo API access patterns, terminology (OSAIPO, FPL, FCA, FOA), writing and git conventions, consent requirements for public-facing actions, and the Fedora AI-Assisted Contributions Policy. This is part of a broader effort to bring `council/tickets` up to parity with sibling project repositories that already have instructions for AI-assisted governance workflow facilitation. Assisted-by: Claude Opus 4.6 (1M context) Signed-off-by: Justin Wheeler <jwheel@redhat.com> |
||
|---|---|---|
| .forgejo/issue_template | ||
| AGENTS.md | ||
| LICENSE.txt | ||
| meeting_agenda.txt | ||
| README.adoc | ||
Fedora-Council/tickets
What is this?
The Fedora Council uses this repository to record on-going work and track tickets which need a specific resolution. Tickets are discussed during regularly-scheduled meetings. For more information about the Council, see the Fedora Council charter.
File a new ticket
To file a new ticket, open a new ticket.
How to contact the Council
You can also find the Fedora Council in the following places:
-
Fedora Discussion: #council tag on Fedora Discussion
-
Fedora Chat/Matrix: #council:fedoraproject.org