Skip to content

Special Interest Groups

Special Interest Groups are a core component of the Rocky Linux community, in which various members of these groups can extend the Enterprise Linux experience, by way of packages, images, and/or other community engagement.

For the case of this wiki, Special Interest Groups are recommended not to have direct wiki pages, but instead maintain their own wiki pages, maintained at the RESF Git Service.

This page serves simply as an overview to Special Interest Groups. See the SIG Guide for specific information such as proposing a SIG, content management, and much more.

See the Current SIGs page for a list of current Special Interest Groups that may or may not be active in the community.

Special Interest Group Requirements

We expect SIGs to satisfy some basic requirements, such as:

  • The group should be related to Rocky Linux, a use-case for Rocky Linux or Enterprise Linux, or related to Enterprise Linux as a whole
  • There must be feedback and control into the Rocky Linux community
  • All communication as to the work of the SIG should be public - Some matters may have to be private, and as such should be out of band
    • It is expected that each SIG will have a public channel as SIG/name in mattermost. Optionally an IRC channel can also be assigned.
  • Code produced within the SIG must be compatible with a FOSS license presently used by Rocky Linux - If a new license is wanted, consult with Release Engineering/Core or the ~Legal channel in mattermost.
  • All documentation and information of the SIG should be on a wiki produced in the RESF Git Service.
  • All documentation produced within the SIG must be a compatible documentation license
  • Groups should be aware/watchful of the direction from the Release Engineering team/Core as it can affect how SIGs operate if they are producing compiled software.

Special Interest Group Wiki

Each SIG should have a wiki that will have documentation for their particular group as well as information on how the group operates. Required information should be as follows:

  • An "about" section on the index that explains what the group does/a group description
  • Mission Statement
  • How to Contribute / Onboarding Process
  • Meeting Information (time, location, other information that they feel is important)
  • Policies and Resources, if applicable

SIG Membership and Participation

The following rules apply for SIG membership:

  • Mailing lists of SIGs are open and can be joined freely
  • SIG members are appointed/approved by SIG sponsors/leaders - The sponsors/leaders typically have write permissions to relevant wikis and git repos
  • SIG sponsors/leaders may be asked to be a mailing list moderator
  • SIG channels will be public under a name such as SIG/name with an optional IRC channel to be bridged.
  • Optionally: define if work with CentOS Stream will be applicable for the SIG

SIG Reporting

SIGs are expected to report at least quarterly, with a brief summary of what they've accomplished. A suggested outline:

  • Membership update (members joined or parted, sponsor/leader changes)
  • Releases in the current quarter (or previous quarter if no releases)
  • General activity or health report
  • Issues to address within the SIG

Joining a Special Interest Group

Joining an established Special Interest Group should be simple. Each SIG will have its own process and outlines. Please see sponsors or other members of the Special Interest Group you're interested in if a wiki or other documentation is not available.



Purpose: Account Services maintains the accounts for almost all components of the Rocky ecosystem

Technology: Noggin used by Fedora Infrastructure

Contact: ~Infrastructure in Mattermost and #rockylinux-infra in Libera IRC


Purpose: General projects, code, and so on for the Rocky Enterprise Software Foundation.

Technology: Gitea

Contact: ~Infrastructure, ~Development in Mattermost and #rockylinux-infra, #rockylinux-devel in Libera IRC


Purpose: Packages and light code for the Rocky Linux distribution

Technology: GitLab

Contact: ~Infrastructure, ~Development in Mattermost and #rockylinux-infra, #rockylinux-devel in Libera IRC


Purpose: Users can apply to be a mirror to host Rocky content (SIG or the base operating system)

Technology: MirrorManager 2

Contact: ~Infrastructure in Mattermost and #rockylinux-infra in Libera IRC


Purpose: Users can subscribe and interact with various mail lists for the Rocky ecosystem

Technology: Mailman 3 + Hyper Kitty

Contact: ~Infrastructure in Mattermost and #rockylinux-infra in Libera IRC