From 06f3ce44439e0530b4a182906a4cc5573ffd5250 Mon Sep 17 00:00:00 2001 From: Pierre-Yves Chibon Date: Mon, 30 Mar 2020 10:26:37 +0200 Subject: [PATCH] Add a blob documenting groups in Fedora Signed-off-by: Pierre-Yves Chibon --- groups_in_fedora.md | 75 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 groups_in_fedora.md diff --git a/groups_in_fedora.md b/groups_in_fedora.md new file mode 100644 index 0000000..8142580 --- /dev/null +++ b/groups_in_fedora.md @@ -0,0 +1,75 @@ +# Groups in Fedora + +## What are the different types of groups? + +Fedora has a few types of groups: +- "tracking" groups +- "shell" groups +- "pkgdb" groups + +* Tracking groups +The tracking groups are primarily meant to indicate that people are contributors +in a certain part of the Fedora Project. +These group will allow new accounts to become CLA+1 which is the way of saying +that someone has signed the FPCA (which used to be called CLA, but the FPCA is +not a CLA, thus the rename) and is a member of one other group. +Being CLA+1 is the criteria the project has set to recognize someone has been +an active contributor. +With this trust comes a few "priviledges" such as: + - Access to the @fedoraproject.org email alias + - Access to fedorapeople.org + - Possibility to vote on some of the elections (including FESCo and the Council) + +* Shell groups +These groups are used when contributors gain access to some of the machines +in the Fedora Infrastructure. +For example, members of the sysadmin group are allowed to commit on the +infrastructure's git repository and this is allowed by giving write access to the +git repository to this group, on the file-system. + +* pkgdb groups +These groups are meant to facilitate the collective maintenance of packages in +Fedora. +In other words, by giving commit access to the group on a package (or set of +packages), everyone in the group can commit to the package and thus the +maintenance of the package can be shared amongs the members of the group. + + +## How to request a group to be created? + +The short answer is to open a ticket on the fedora-infrastructure issue tracker: +https://pagure.io/fedora-infrastructure/ + +It is unlikely you will need to create "shell" group, but you can ask for the +creation of a "tracking" or "pkgdb" group. + +### "pkgdb" groups name + +In the days where pkgdb was an application in addition to a type of group, groups +meant to share the collaboration of packages had to end with `-sig`. +This is technically no longer a requirement today, however, it remains a standard +we try to maintain as it makes it easier to identify "pkgdb" group by their +names. + +**When requesting a "pkgdb" group, please try to adhere to this standard.** + +### "pkgdb" groups and mailing list + +"pkgdb" groups are created to maintain packages. They are meant to be CC'ed on +bugzilla tickets associated with these packages. +The tools syncing the information from dist-git to bugzilla uses the +"mailing list address" field in the group's settings. + +This means that the email address associated with the group will be notified of +every bug reports opened against all the packages the group maintain, including +security sensitive reports. + +In consequence, it is highly recommended that the email set in the "mailing list +address" in the group's settings in FAS be something that does not have publicly +accessible archives. + +A simple answer to this is to create a new mailing list when creating the "pkgdb" +group. This list can then be made private and invite-only. + +**When requesting a pkgdb group, please let us know if you need a new mailing list +to be created or not.**