Skip to content

Proposing a SIG

This page goes over proposing a Special Interest Group for the Rocky ecosystem. Anyone can propose or participate in a Special Interest Group.

Proposal

Creating a new Special Interest Group requires participation from a member of the Rocky teams or a member of the board. A SIG must meet these requirements:

  • The group must be related to Rocky or a use-case for Rocky or 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

    • 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 and upstream - If a new license is wanted and is not available in the upstream list, consult with Release Engineering/Core or ~Legal in Mattermost.

  • 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.
  • A member of the SIG should also come from the Core/RelEng team, in the case that the SIG produces packages for use on a Rocky system.

Proposal Process

It is up to the requestor to:

  • Check and verify that the topic of interest is already covered by an existing Special Interest Group within Rocky or CentOS Stream

  • Post an introductory RFC message:

    • As an email to the rocky-devel mailing list and ask for comments or...
    • As a message to SIG/general in mattermost

Upon approval or general acceptance, it is up to the requestor or a Core/RelEng member to open a ticket for creating the initial resources at the SIG/Core Tracker using a predefined template:

  • RESF Git Service organization is created (git.resf.org)
  • Rocky Linux GitLab groups are created (git.rockylinux.org) if applicable
  • groups in Rocky Account Services
  • mail list
  • channel in mattermost + IRC channel as a bridge if requested
  • Bug Tracker project

A copy of the proposal or another version of it that is related to the original request should be in the request.

Acceptance

TBD

Resources

URL: https://accounts.rockylinux.org

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

URL: https://git.resf.org

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

URL: https://git.rockylinux.org

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

URL: https://mirrors.rockylinux.org

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

URL: https://lists.resf.org

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

Last update: 2023-03-23