On Mon, Dec 13, 2021 at 09:40:19AM -0500, Stephen John Smoogen wrote: > It is a fairly manual process where a person volunteers to sit in > front of the firehose every day and deal with these requests. The > person who has to process them has a checklist of policy items they > have to confirm/check to make sure the branch is possible. Where is that checklist? I found https://docs.pagure.org/releng/sop_process_dist_git_requests.html, but it refers to a tool which is deprecated in favor of another one, at https://pagure.io/fedscm-admin/, but none of those places have a clear articulation of the policy items. I get human sanity check of new package requests is good, although really ideally I would hope that wouldn't fall to the rel-eng/scm firehose volunteers. But it seems like "request an EPEL branch" should generally be either "Okay! Doing that automatically now" or "Oh, this is in EL, sorry"*. What are the other cases? * I'm very sad that this isn't "So, would you like to do it anyway, and then make a module?", but c'est la vie -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
