Re: Proposing an EPEL packaging SIG

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2020-09-11 at 15:44 -0400, Neal Gompa wrote:
> On Fri, Sep 11, 2020 at 3:10 PM Robbie Harwood <rharwood@xxxxxxxxxx>
> wrote:
> > Michel Alexandre Salim <michel@xxxxxxxxxxxxxxx> writes:
> > 
> > > * Have an expedited flow where this SIG can request EPEL branches
> > > and
> > > admin access to packages if there are no response from package
> > > maintainers for a set period (3 days? 1 week?)
> > >   * whether it should be full admin access or whether such access
> > > should be scoped to epel* branches can be discussed. Full admin
> > > would
> > > make it possible to adjust the spec in Rawhide to be more EPEL
> > > friendly, for example
> > 
> > Unless I've missed something, we still don't have per-branch ACLs
> > in
> > dist-git.
> > 
> > I don't think it's okay to force maintainers to give you admin or
> > commit
> > to their packages just because you want them in EPEL.
> > 
Fair enough, I think if the maintainer does not explicitly grant
permission, any automatic grant should be limited to epel-* branches.

> > (I'm also not one of the kind of people who really like having one
> > spec
> > file for all versions of the package, but I know others disagree
> > with me
> > on this.  Certainly if hypothetically I didn't want to maintain an
> > EPEL
> > package I wouldn't want its logic /also/ foisted on me in rawhide.)
> > 
Yeah. I'm in-between on this, I try to get changes into the Rawhide
branch if they are not too intrusive, and keep them in the EPEL
branches if they are. EPEL maintainers can always just submit a PR
against the Rawhide branch so not having automatic access is no big
deal.

> 
> We have per-branch ACLs in Dist-Git since early August. The
> collaborator role in Pagure lets you grant people commit access for
> specific branches.
> 
Yeah, the collaborator role is what I had in mind but I didn't remember
the exact name when writing it (should have just looked it up in
src.fedoraproject.org). Thanks Neal!

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/michel@xxxxxxxxxxxxxxx
chat via email: https://delta.chat/
GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux