🤖 docs(AGENTS): Add AI agent context for Council Tickets tracker #571

Merged
jflory7 merged 1 commit from add/agents-md into main 2026-07-09 18:07:08 +00:00
Owner

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.

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.
jflory7 added this to the Fedora Linux 45 milestone 2026-07-02 03:47:51 +00:00
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>
pbokoc approved these changes 2026-07-09 14:37:50 +00:00
pbokoc left a comment

I don't really have much experience with this, but LGTM I guess :)

I don't really have much experience with this, but LGTM I guess :)
Author
Owner

@pbokoc I think the most important thing is that the information in the file is not outright wrong or incorrect.

Beep boop! 🤖 The robots are here. 😛 Merging! 🌊

@pbokoc I think the most important thing is that the information in the file is not outright wrong or incorrect. Beep boop! 🤖 The robots are here. 😛 Merging! 🌊
jflory7 self-assigned this 2026-07-09 18:06:57 +00:00
jflory7 deleted branch add/agents-md 2026-07-09 18:07:08 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
council/tickets!571
No description provided.