From babaaabcd566954010cae6f1f1702ba413b95a10 Mon Sep 17 00:00:00 2001 From: Troy Dawson Date: Mar 29 2024 21:35:34 +0000 Subject: Rewrite EPEL Packagers SIG page --- diff --git a/modules/ROOT/pages/epel-packagers-sig.adoc b/modules/ROOT/pages/epel-packagers-sig.adoc index 03a0867..2ed8164 100644 --- a/modules/ROOT/pages/epel-packagers-sig.adoc +++ b/modules/ROOT/pages/epel-packagers-sig.adoc @@ -5,41 +5,34 @@ include::partial$attributes.adoc[] [[epel_packagers_sig]] == About -EPEL (Extra Packages for Enterprise Linux) creates, maintains, -and manages a high quality set of additional packages for Enterprise -Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), -CentOS and Scientific Linux (SL), Oracle Linux (OL). - -This EPEL Packagers SIG is a subset of maintainers that are primarily focused ensuring -the availability of certain packages that users care about, including -their stack of dependencies; we basically want to fill the gap caused by -the different workflows for Fedora and EPEL: - -* Fedora packages get automatically branched for every upcoming Fedora -release -* Fedora package maintainers are expected to support every extant Fedora -release, plus the upcoming release branch and the development branch -(Rawhide) - -Given that EL releases have a much longer lifecycle, there is no -requirement that Fedora package maintainers care about EPEL, and no -automatic branching: - -* The set of packages that are relevant might be different for different -releases, especially for non-leaf dependencies -* It is more difficult to maintain packages across different EPEL -releases -* EL use cases often diverge from Fedora use cases - -This often means there is a lag between a new Enterprise Linux release +EPEL Packagers SIG is a sub-project of EPEL. You do not need to +be a member of the EPEL Packagers SIG to build packages on EPEL. + +Being a member of the EPEL Packagers SIG does not give you any +extra permissions. It is not like Fedora's Proven Packager. + +EPEL Packagers SIG is a dist-git group. Being a member of that +group allows you to work with packages that have added the +https://src.fedoraproject.org/group/epel-packagers-sig[epel-packagers-sig group] +as a collaborator on their packages. You will be able to +branch, build and work on those packages. + +== Why + +There is often a lag between a new Enterprise Linux release being available, and extra packages being available for it: -* that package has to be branched -* if it has not been branched for EPEL before, the existing maintainers -have to decide if they want to support EPEL or not -* rinse and repeat for every dependency +* That package has to be branched and built +* The existing maintainers have to decide if they want to support the latest EPEL or not +* Rinse and repeat for every dependency +* Then have years of maintenance and updates for that package + +Adding the epel-packagers-sig group as a collaborator for a package +gives the regular package maintainer(s) more people to maintain it +over the years. It also gets the package into the latest version +of EPEL faster. -=== Workflow +== Workflow We aim to be somewhere in between the language-based SIGs (e.g. the https://fedoraproject.org/wiki/SIGs/Python[Python SIG]) and being "provenpackagers for EPEL": @@ -59,6 +52,8 @@ updates. Automatic branching is not implemented yet. +=== Packages + Candidate packages for onboarding -- https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=days_elapsed&list_id=11600601&o1=greaterthan&product=Fedora&product=Fedora%20EPEL&query_format=advanced&short_desc=epel&short_desc_type=allwordssubstr&v1=14[NEW branch requests over two weeks old]. We should consider reviewing this @@ -73,27 +68,26 @@ See xref:epel-policy.adoc#stalled_epel_requests[the guidelines for stalled requests] for follow-ups if a branch request has been stale for at least a week. -[[how_can_i_contribute]] -== How can I contribute? - -We are always looking for interested folks to help out! See the main -xref:epel-help.adoc[Joining EPEL] page for more information on how -to join EPEL. - -=== Join the EPEL Packagers SIG +== Joining the EPEL Packagers SIG Getting added to `epel-packagers-sig` grants collective access to all packages this group has access to, so we do need to be more careful when -adding new contributors to this group. The procedure is similar to that -for -xref:fesco::Provenpackager_policy.adoc#_becoming_provenpackager[provenpackagers]. +adding new contributors to this group. + +A candidate should be a skilled package maintainer who is experienced +in a wide variety of package types and who are familiar with the +xref:fesco::Package_maintainer_responsibilities.adoc#[Fedora packaging guidelines] +and xref:epel-policy.adoc[EPEL package maintainer policies], + +The procedure is similar to that +for xref:fesco::Provenpackager_policy.adoc#_becoming_provenpackager[provenpackagers]. * File a ticket in the https://pagure.io/epel/issues[EPEL issue tracker] indicating why you wish to become a member. -* A Packagers SIG member will send an e-mail to the sponsors, so they +* A Packagers SIG member will send an e-mail to the SIG members, so they are aware about the ticket. -* Sponsors vote in the EPEL ticket. -* You must get at least 1 positive votes from sponsors with no negative +* SIG members vote in the EPEL ticket. +* You must get at least 1 positive votes from SIG members with no negative votes, over a one week review period, to be approved. If you haven’t been approved after one week, the EPEL Steering Committee will vote