From c70d7de652a80bbd40cb4c4d7870ced1db23a6a4 Mon Sep 17 00:00:00 2001 From: Michel Lind Date: Nov 13 2024 20:46:52 +0000 Subject: Update EPEL package request to add clarity for existing maintainers and releng For consistency in handling EPEL package requests, document needed steps for existing maintainers and for releng. Also make the request templates more consistent between regular packagers and EPEL Packagers SIG members. Finally, put an advisory note to not request access via the SIG route for now while the workings are being reviewed. Signed-off-by: Michel Lind --- diff --git a/modules/ROOT/pages/epel-package-request.adoc b/modules/ROOT/pages/epel-package-request.adoc index 23d4274..35c7075 100644 --- a/modules/ROOT/pages/epel-package-request.adoc +++ b/modules/ROOT/pages/epel-package-request.adoc @@ -79,6 +79,8 @@ Clear out Description and put .... Please branch and build in epel9. + +Please refer to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#existing_maintainers for additional details. .... If there is no response after a week, add the following comment in the bug. @@ -102,6 +104,11 @@ If you do not wish to maintain in epel9, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS ); please add me through https://src.fedoraproject.org/rpms//adduser + +(optionally, if there's not a separate Bugzilla assignee for EPEL) +I can be the primary contact for EPEL (FAS: ). + +Please refer to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#existing_maintainers for additional details. .... If there is no response after a week, add the following comment in the bug. @@ -123,6 +130,7 @@ If there is no action on the bug after two more weeks, follow the xref:epel-poli Per the EPEL stalled package policy - https://docs.fedoraproject.org/en-US/epel/epel-policy/#stalled_epel_requests - I have contacted the maintainer, twice, and waited the appropriate amount of time. I am requesting be given commit permissions so that I might branch and build this package in epel9. +Please refer to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#releng for additional details. .... @@ -132,6 +140,13 @@ After you have been given commit permissions, you can then branch, build, and ma [[epel_packagers_sig_members]] === EPEL Packagers SIG members +[NOTE] +.EPEL Packagers SIG under review +==== +The working of this SIG is currently being reviewed. Please hold off +requesting access via the SIG until this is resolved. +==== + Clear out Description and put .... @@ -145,10 +160,13 @@ https://src.fedoraproject.org/rpms//addgroup and grant it commit access, or collaborator access on epel* branches. (optionally, to request access for yourself) -I would also be happy to be a co-maintainer (FAS: ). +I would also be happy to be a co-maintainer (FAS: ); +please add me through https://src.fedoraproject.org/rpms//adduser (optionally, if there's not a separate Bugzilla assignee for EPEL) I can be the primary contact for EPEL (FAS: ). + +Please refer to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#existing_maintainers for additional details. .... If there is no response after a week, add the following comment in the bug. @@ -170,8 +188,48 @@ If there is no action on the bug after two more weeks, follow the xref:epel-poli Per the EPEL stalled package policy - https://docs.fedoraproject.org/en-US/epel/epel-policy/#stalled_epel_requests - I have contacted the maintainer, twice, and waited the appropriate amount of time. I am a member of the epel-packagers-sig and I am requesting epel-packagers-sig be given commit permissions so that I, or a member of the SIG, might branch and build this package in epel9. Please also add my account: . +Please refer to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#releng for additional details. .... After the epel-packagers-sig has been given commit permissions, you can then branch, build, and maintain the package in epel. + +[[handling_epel_requests]] +== Handling EPEL package requests +[[existing_maintainers]] +=== For package maintainers + +If you would like to handle a branch and build request yourself, see the https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/#working_with_branches[working with branches] section of the Package Maintenance Guide. + +If the requester volunteers to co-maintain the package, any existing +comaintainer with admin access can add them via +https://src.fedoraproject.org/rpms//adduser . + +Similarly, to add a packager group to the package, use +https://src.fedoraproject.org/rpms//addgroup . + +Do note that +- if you grant commit access, the grantee can also commit to Fedora branches +- if you grant collaborator access, the grant needs to be to `epel*` to + future proof this for future releases + +If the existing comaintainers do not want to maintain the package in EPEL +at all, the person or group mentioned in the request can be made the +Bugzilla assignee for that package. Note that only the main admin can set this. + +Do check with https://docs.fedoraproject.org/en-US/fesco/SIG_policy/[SIG policy] +to see if the mentioned SIG has a policy for co-maintaining packages or not. + +[[releng]] +=== For releng +When handling a xref:epel-policy.adoc#stalled_epel_requests[Stalled EPEL Request] + +- make sure that due process has been observed (bug filed, ping after a week, + and at least two weeks since the ping) +- if the the request is to add both a person and a group to the package, make + sure to add both + +For packages that have collaborator access set to anything other than `epel*`, +someone who is a collaborator directly or indirectly via group membership may +file a ticket to ask releng to set this to `epel*`.