Special Interest Groups are a core piece of the Rocky Linux community, in which
various members of these groups can extend the Enterprise Linux experience, by
way of packages, images, or other community engagement.
For the case of the wiki, Special Interest Groups are recommended not to have
direct wiki pages, but instead maintain their own set of GitLab pages in the form
of a wiki.
This page will serve as informational only on current and proposed SIG’s, as
well as information on proposing a SIG.
|Core||Rocky Linux maintainers, packagers, and developers. It is primarily a mix of Release Engineering and Infrastructure|
|AltArch||Maintains alternative architectures that is not directly supported by Rocky Linux|
|Desktop||Supports and maintains the desktop experience for Rocky Linux|
|Legacy||Supports and maintains legacy hardware support for Rocky Linux|
|HPC||Maintains High Performance Computing support for Rocky Linux|
|Cloud||Cloud images and infrastructure - May work upstream with Stream for openstack and others as well|
|Leapp||Focuses on the leapp framework to facilitate upgrades between major versions of Rocky|
We expect SIGs to satisfy some basic requirements, such as:
The group must be related to Rocky, a use-case for Rocky, or related to Enterprise Linux as a whole
There must be feedback and control into the Rocky 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
SIG/namein 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 - If a new license is wanted, consult with Release Engineering/Core or the
~Legal channel in mattermost.
All documentation produced within the SIG must be a compatible documentation license
All documentation and information of the SIG should be on a wiki produced in git.
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.
Optionally: define if work with CentOS Stream will be applicable for the SIG
Each SIG should have a wiki that will have documentation for their particular group as well as information on how the group operates. Minimum required information should be as follows:
The following rules apply for SIG membership:
SIG/namewith an optional IRC channel to be bridged.
SIGs are expected to report at least quarterly, with a brief summary of what they’ve accomplished. A suggested outline: