Strengthen the Gem definition based on systematic analysis of the first real use (2026-04-21 Docs Team meeting), where the AI output deviated from Fedora community conventions in ways the original definition did not anticipate. New `<conventions>` section encodes seven categories of rules: - People references: `FirstName (@username)` in exec summary, bare `@username` in detailed log - Ticket references: `### Ticket:` prefix with linked Forgejo cross-repo shorthand (`org/repo#number`) - Proper nouns: correct capitalization (AsciiDoc, Quick Docs) - Fedora org naming: "Mindshare branch" not "Mindshare & Outreach" - Off-topic tangents: omit unless they produce outcomes - Completed action items: auto-strikethrough for "post summary" - Topics list: substantive topics only, no housekeeping New `<example>` section provides condensed excerpts from the golden reference demonstrating all key conventions. This gives the Gem few-shot learning signal for the specific patterns it got wrong, without embedding the full 100+ line example inline. New template fidelity constraint explicitly requires matching heading levels, bullet styles, and link syntax from the template. Context section now references the golden example file as a knowledge file for the Gem to consult. Assisted-by: Claude Opus 4.6 (1M context) Signed-off-by: Justin Wheeler <jwheel@redhat.com> |
||
|---|---|---|
| docs | ||
| examples | ||
| knowledge | ||
| templates | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| definition.md | ||
| LICENSE.txt | ||
| README.adoc | ||
| REDHAT.md | ||
Meeting Secretary
Reusable AI prompts and knowledge files for summarizing Fedora Meetbot meetings into Fedora Discussion topics and Forgejo ticket comments.
About
Meeting Secretary is a collaborative project for reusable prompts and AI/LLM tools that streamline Fedora community meeting workflows. The primary artifact is a Google Gemini Gem that transforms Meetbot HTML log files into structured Markdown outputs:
-
Fedora Discussion summary posts — comprehensive meeting recaps with executive summary, action items, and detailed chronological log.
-
Forgejo ticket comments — concise per-ticket updates with follow-up items, linking back to the full discussion topic.
The Gem follows a fire-and-forget workflow: provide the Meetbot log files, the Gem analyzes them and produces all outputs as ready-to-copy Markdown blocks.
Repository Layout
| Path | Purpose |
|---|---|
|
Core Gem system prompt |
|
Gem knowledge files (Fedora team registry, Meetbot command reference) |
|
Output templates (Discourse post, Forgejo comment) |
|
Sample input HTML logs and expected output Markdown |
|
Design specs and agentic SDLC reference material |
|
Project context for AI assistants |
|
How to contribute |
|
Red Hat AI policy reference |
|
CC BY-SA 4.0 |
Quick Start
-
Set up a Google Gemini Gem (or compatible LLM tool).
-
Copy the contents of
definition.mdas the Gem’s system prompt. -
Attach the files in
knowledge/as knowledge context to the Gem. -
Attach the files in
templates/as knowledge context to the Gem. -
Provide a Meetbot HTML log file to the Gem.
-
Copy the generated Markdown outputs to Fedora Discussion and Forgejo.
Customization
The modular design makes it easy to adapt Meeting Secretary for your team:
-
Templates: Fork and edit files in
templates/to change the output format, greeting style, or section structure. -
Knowledge files: Update
knowledge/teams.mdto add or correct team information. -
Examples: Add your team’s meeting logs and validated outputs to
examples/to build a shared corpus.
See CONTRIBUTING.md for full contribution guidelines.
License
CC BY-SA 4.0 © Justin Wheeler, Fedora AI/ML SIG, & Fedora community.