Creating a Fedora SIG

Nancy Nwankwo, Justin Wheeler, Fedora community contributors Version 1.0 Last review: 2025-10-29

This page provides instructional steps on how to start a Fedora SIG using current communication platforms and tools.

A Fedora Special Interest Group (SIG) is a group of people who share an interest in a specific topic or project within Fedora. SIGs are easy to start and offer a great way to collaborate and work together on things you are passionate about, such as a new idea, project, or community effort. This guide will show you the simple steps to create your own SIG using available tools and resources.

Step 1: Explore Other SIGs & Subprojects

You don’t have to reinvent the wheel! Other SIGs may already be tackling related ideas or have systems in place that you can learn from. Reach out and collaborate!

Examples:

Step 2: Get Others Interested

Before creating a SIG, confirm that at least a few other Fedora contributors are interested in the topic. You can:

  • Post on Fedora Discussion (using the appropriate category or tag) and the Fedora devel mailing list.

  • Join a relevant Fedora Chat/Matrix room and share your ideas. The Fedora devel mailing list is a good place to start if you are not sure of what group to join. Many Fedora developers and packagers can be found there.

Your post should clearly explain:

  • What your proposed SIG is about

  • Why it matters

  • How others can get involved

Example titles
“Looking to start a Fedora Edge Computing SIG, anyone interested?”
“Fedora for Students SIG: anyone want to join?”

Step 3: Set Up the Basics

Once there is enough interest, establish your SIG’s basic footprint in Fedora’s ecosystem. This helps others find you and contributes to long-term sustainability.

Required Setup

  • Create a tag on Fedora Discussion (to organize conversations).

  • Request a Fedora Chat/Matrix room. If a related room exists or there isn’t much traffic yet, use the existing room and wait until there’s enough interest to request a new one.

  • Create a Forgejo repository or project board (optional but useful for tracking tasks).

  • Create a private mailing list for Bugzilla bugs (required for SIGs that maintain packages).

If you are unsure where to start, the Fedora Join SIG can assist.

Create a dedicated Fedora Discussion tag for your SIG early on. It helps organize all related topics and makes your group easier to discover. Drop into community-wide Fedora Chat/Matrix rooms like #social:fedoraproject.org or #join:fedoraproject.org for community social chatter and quick help.

Step 4: Document the SIG

Create a Fedora Docs site that introduces your SIG. The Fedora Docs site index page should include:

  • The SIG’s mission and scope

  • A list of communication channels

  • Links to resources (Fedora Discussion tag, Fedora Chat/Matrix room, Forgejo repo, etc.)

  • How others can join or contribute

  • Team leads or go-to people

You may:

  • Publish this on the Fedora Docs page (recommended)

  • Or as part of your Forgejo README

While Fedora Wiki is still in use, SIGs are starting to move their documentation to Fedora Docs. Fedora Docs are better because they are easier to find information and show up better in search results.

Step 5: Plan Your First Activities

SIGs gain momentum by working together toward shared goals. Early actions might include:

  • Tracking to-do items in a Forgejo issue board

  • Organizing an async planning thread in Fedora Discussion

  • Hosting a regular or one-time Fedora Chat/Matrix meeting

You can also:

  • Submit articles to Fedora Magazine to promote what your SIG is doing in Fedora

  • Share contributor journeys and milestones on the Community Blog

  • Ping the Marketing Team for help with graphics, campaign ideas, and event promotion

  • Get community planning and coordination tips from the Community Ops team

  • Reach out to other related SIGs for cross-group support

Further Reading:

Step 6: Keep It Going

Successful SIGs grow by being active, inclusive, and goal-driven. Some tips:

  • Review progress regularly (monthly/quarterly) and share public reports on progress.

  • Actively welcome and onboard new contributors with documentation for newcomers and/or designated mentors to help onboard new contributors to the community.

  • Share your progress publicly via blog posts, social media, local outreach, or mailing list.

  • Define leadership roles or points of contact for long-term sustainability.

Need inspiration? Check out well-run SIGs like Fedora CoreOS for best practices.

Step 7: Where to Get Help

You are not doing this alone! Fedora has a helpful, friendly community and lots of places where you can ask questions, get guidance, and find people to work with. Here is a quick decision path:

I need help with… Try reaching out to…

Setting up SIG tools

Join SIG, Infra Team

Finding collaborators

Fedora Discussion, Join SIG

Writing docs or onboarding guides

Docs Team, Community Ops

Promotion & outreach

Marketing Team, Fedora Magazine

Hosting meetings or async planning

Fedora Chat/Matrix rooms, Community Blog

Ending or pausing a SIG

Fedora Council, Join SIG

Want to help? Learn how to contribute to Fedora Docs ›