On Fri, Sep 11, 2020 at 03:50:58PM -0700, Michel Alexandre Salim wrote: > We discussed the proposal a bit at today's EPEL SC meeting; here's a > revised proposal taking into account the suggestions from the meeting > and earlier in this list. > > ## The SIG > - bstinson pointed out that epel-wranglers was started to address the > same issue, we can resurrect that > - we want to limit the access to epel* branches only, not all branches, > as suggested both here and at the meeting. Any change the epel- > wranglers want to make to the Rawhide branch can be done as a PR > - the EPEL branch will likely diverge from master over time anyway > - the collaborator permission (available since August, yay) can be used > for such granular access > - nirik pointed out that collaborators can't yet request new > branches, if the proposal is approved we can work on making the `fedpkg > request-branch` flow support this > - carlwgeorge suggested getting the group up and running first, and > working on automation later > > ## Workflow > - no objection that I recall to having epel-wranglers automatically get > access if the Fedora maintainers do not respond (so we can circumvent > needing to do a non-responsive maintainer request) > - we probably won't have this automated at the beginning, see above > - down the line, epel-wranglers need to decide on what to do with > releases they no longer want to support (e.g. when everyone involved > only cares about epel10 and epel9 and there's a CVE affecting epel8). > the normal orphan process probably works - we announce the package is > being orphaned by the group on epel-devel +1 for the proposal. The group-maintenance approach is being used more and more, and it seems good to use that also for EPEL. I'd be happy to give access to any and all epel branches on my packages to the SIG. Zbyszek > Let's continue discussing the proposal in this thread, as suggested > during the meeting. > > Thanks all, _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
