PR#335: Remove packaging SIGs section from request guide - epel

epel

#335 Remove packaging SIGs section from request guide

Merged 21 days ago by tdawson. Opened a month ago by carlwgeorge.

carlwgeorge/epel request-package-remove-packaging-sigs into main

Remove packaging SIGs section from request guide

Carl George • 21 days ago

320d7e0

modules/ROOT/pages/epel-package-request.adoc

file modified

-69

		`@@ -151,75 +151,6 @@`

		`After you have been given commit permissions, you can then branch, build, and maintain the package in epel.`

		`- [[members_of_packaging_sigs]]`
		`- === Members of Packaging SIGs`
		`-`
		`- Only use this with the consent of the packaging SIG in question - this normally`
		`- means you are either a member of the SIG, or that SIG's policy requires blanket`
		`- ownership of packages (e.g. Rust and Go SIGs should be added to all packages`
		`- written in those languages, but might not automatically be added if the name of`
		`- the package deviates from the general convention).`
		`-`
		`- e.g.`
		`-`
		- * link:++https://fedoraproject.org/wiki/SIGs/Go++[Go] (`go-sig`)
		- * link:++https://fedoraproject.org/wiki/SIGs/MkDocs++[MkDocs] (`mkdocs-sig`)
		- * link:++https://fedoraproject.org/wiki/SIGs/Python++[Python] (`python-packagers-sig`)
		- * link:++https://fedoraproject.org/wiki/SIGs/Rust++[Rust] (`rust-sig`)
		`-`
		- Clear out `Description` and put in:
		`-`
		`- [,console]`
		`- ----`
		`- Please branch and build <package> in epel9.`
		`-`
		`- If you do not wish to maintain <package> in epel9,`
		`- or do not think you will be able to do this in a timely manner,`
		`- the <sig name> SIG would be happy to be a co-maintainer of the package;`
		`- please add the <sig group name> group through`
		`- https://src.fedoraproject.org/rpms/<package>/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: <my_FAS_id>).`
		`-`
		`- (optionally, if there's not a separate Bugzilla assignee for EPEL)`
		`- I can be the primary contact for EPEL (FAS: <my_FAS_id>).`
		`- ----`
		`-`
		`- If there is no response after a week, add the following comment in the bug.`
		`-`
		`- [,console]`
		`- ----`
		`- Will you be able to branch and build <package> in epel9?`
		`- The <sig name> SIG would be happy to be a co-maintainer`
		`- if you do not wish to build it on epel9.`
		`- ----`
		`-`
		`- If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[stalled EPEL request steps], and open a ticket with link:++https://pagure.io/releng/issues/++[releng]`
		`-`
		`- * Ticket Title:`
		`- +`
		`- [,console]`
		`- ----`
		`- Stalled EPEL package: <package>`
		`- ----`
		`-`
		`- * Ticket Body:`
		`- +`
		`- [,console]`
		`- ----`
		`- * Describe the issue`
		`- <package> is a stalled EPEL package.`
		`- Per the EPEL stalled package policy - https://docs.fedoraproject.org/en-US/epel/epel-package-request/#stalled_epel_requests - I have contacted the maintainer, twice, and waited the appropriate amount of time.`
		`- <Bugzilla URL>`
		`- I am a member of <sig group name> 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: <my_FAS_id>.`
		`-`
		`- <Fill out the other sections as you see fit>`
		`- ----`
		`-`
		`- After the SIG has been given commit permissions, you can then branch, build, and maintain the package in EPEL.`
		`-`
		`[[stalled_epel_requests]]`
		`== Stalled EPEL requests`

carlwgeorge commented a month ago

While some SIGs may allow any member of the SIG to request an EPEL branch for a package, that is up to the SIG to document and communicate among themselves. The general guidelines for requesting packages should standardize on direct maintainership.

Fixes: #333