SIG policy

In order to make the maintenance of large, interconnected package ecosystems easier for members of the associated Special Interest Groups (SIGs), FESCo can decide to automatically apply rules to both existing and new packages that meet some specified criteria.

Go SIG

The Go SIG group (@go-sig) MUST be granted the commit or admin ACLs on all Go packages. A Go package is defined as any package that directly BuildRequires golang, golang-bin, or go-rpm-macros. Note that %gometa automatically inserts BuildRequires: go-rpm-macros, so packages that use that macro are also included in this policy.

R SIG

The R SIG group (@r-maint-sig) MUST be granted commit or admin ACLs on the R package and all add-on packages (i.e. any package that matches R-*).

Packages which only contain R code, but are not R add-on packages, will never be packaged as R-*, so they are not covered by this policy (for example, emacs-common-ess, or openms).

The R SIG group (@r-maint-sig) MUST be granted at least the commit ACL on non-add-on packages and applications that call into the R language via its C API (i.e. any package that does not match R-* but links against libR.so).

Rust SIG

The Rust SIG group (@rust-sig) MUST be granted at least the commit ACL on all packages for Rust crates (i.e. any package that matches rust-*).

Packages which only contain Rust code, but which are not Rust crates, will never be packaged as rust-*, so they are not covered by this policy (for example, firefox, thunderbird, or librsvg2).

Packages for Rust applications, which are not published on — and packaged from — crates.io), MUST never be packaged as rust-* according to the Rust Packaging Guidelines (for example, keylime-agent-rust or zola), so they are also not covered by this policy. However, the maintainers of such packages can still opt into granting commit or admin ACL to the Rust SIG group.