Justin Wheeler
010ddb13d2
Refine the description text for the "Context & Background" field in @ananya's issue template to lead with a direct problem-statement question: "What problem does this task solve, or why is it needed?" This acts on feedback from @ananya in her review of PR #164, where she suggested adding a "Gap / Problem Statement" field to make it easier to trace task impact during quarterly reviews. Rather than adding a new field (the template already has eight), the existing field's description was sharpened to prompt for that same information upfront while preserving the emphasis on explaining the "why" behind each task. Assisted-by: Claude Opus 4.6 (1M context) Signed-off-by: Justin Wheeler <jwheel@redhat.com> |
||
|---|---|---|
| .forgejo/issue_template | ||
| AGENTS.md | ||
| CONTRIBUTING.adoc | ||
| LICENSE.txt | ||
| README.md | ||
Community Ops Intern Command Center
Welcome to the Intern Command Center for Fedora Community Operations! This repository is used for planning, tracking, and discussing Fedora Mentored Projects supported by Red Hat Community Architects and mentors from the Fedora Community Ops Team.
What happens here
This repository serves as a central hub for internship project management. Mentors and interns use the issue tracker to plan work, define acceptance criteria, and track progress through two-week sprint cycles. The repository supports both Red Hat and Outreachy internships organized through the Fedora Mentored Projects program.
Current interns (2026)
Ananya Nalavathu
Red Hat OSAIPO Community Architect Intern (March--October 2026). Focus areas include event storytelling (Flock 2026 Afterburn, Waterford Release Party), social media and content creation, Fedora data and analytics, and academic thesis research.
Francois Gonothi Toure
Outreachy Intern with the Fedora Mentored Projects program (May--August 2026). Building a RAG (Retrieval-Augmented Generation) pipeline for Fedora RPM packaging using RamaLama.
Past interns
2024
- Adrian Edwards (
@moralcode) -- Red Hat Community Architect Intern. - Oluwatosin "Tosin" Olatunji (
@tosindoreen) -- Outreachy Intern, Fedora Community Architect. - Roseline Bassey (
@roseline-bassey) -- Outreachy Intern, Fedora Community Architect.
How we work
- Sprint cycles: The internship period is divided into two-week sprints, each tracked as a milestone in the issue tracker.
- Issue templates: Each intern has a personalized issue template that structures tasks with objectives, acceptance criteria, strategic alignment, and self-reflection prompts.
- Weekly stand-ups: Interns prepare a weekly report (seven minutes max) covering in-progress work, other accomplishments, upcoming plans, and blockers.
- Kanban board: The issue board provides a visual overview of task progress across pending, in-progress, and completed states.
Labels
The issue tracker features exclusive labels and regular labels.
An exclusive label belongs to a group identified by a / prefix, and only one label from each group can be applied per issue.
| Group | Values | Description |
|---|---|---|
function/ |
analytics, communications, docs, events, onboarding, operations |
The type of work or skills needed to address an issue. |
needs/ |
triage, changes, reporter feedback, team vote |
Issues where action or more information is needed. |
scope/ |
bug, improvement, new |
The nature of the work. Helps track the ratio of new projects to maintenance of existing ones. |
state/ |
approved, blocked, duplicate, invalid, ready for review, wontfix |
The current status of an issue. Some of these labels trigger different behaviors on the issue board. |
Two additional unscoped labels -- good first issue and help wanted -- are available for discovery.
Communication
- Fedora Community Ops Matrix Room (
#commops:fedoraproject.org) - Fedora Mentored Projects Matrix Room (
#mentoring:fedoraproject.org) - Fedora Discussion -- topics tagged
#mentored-projects-team
Legal
All content in this repository is shared under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.