[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-26 Thread Martin Dummer
Am 22.07.22 um 21:10 schrieb Joonas Niilola: ..., via Github PR or other means. I'd say pushing these experimental packages is rather rare (for proxied people at least), and can also be added without KEYWORDS for example. I agree here. And I think the proxy maintainers can open PRs like now

Re: [gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-26 Thread Zoltan Puskas
Hey, > > How would you suggest we track who has commit access, etc? The same > way we do with developers, via a developer bug? I believe proxy maintainers already have a bug assigned to them (at least I have one), so maybe just a comment or a special tag would be suffient on these bugs to

[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-23 Thread Andreas K. Huettel
> Once again new council has been elected: congratulations to the chosen > members! And once again many nominees expressed their wishes to see more > non-developer contributors to become official developers. Yet, only very > few people (if any) are interested in mentoring them. I get it, the >

[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-23 Thread Andreas K. Huettel
> > 2nd RFC: Recruiting proven contributors without a mentor > > I'm aware recruiters don't really need to ask a permission here, but I > believe it's great to gauge the general feelings about this beforehand. > What would you say if recruiters started more actively approaching > potential

[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-22 Thread Joonas Niilola
On 22.7.2022 21.32, Robin H. Johnson wrote: > > BUT, we can't write a simple gitolite ACL that limits the content within > profiles/package.mask or other files in profiles/ (we can write hooks > that might be able to do this, but that still requires the challenge of > validation inside the file).

[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-22 Thread Robin H. Johnson
On Fri, Jul 22, 2022 at 02:56:33PM +0300, Joonas Niilola wrote: > Cross-posting to gentoo-dev and -project lists due to technical and > non-technical nature. Reply-to is set to -project. ... > 1st RFC: "Trusted contributor model" > > I'm proposing us to giving special commit access to our

[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-22 Thread Joonas Niilola
On 22.7.2022 21.18, Matt Turner wrote: > > How would you suggest we track who has commit access, etc? The same > way we do with developers, via a developer bug? > > I ask because I've noticed a lot of inactive proxied maintainers—one > of which had been listed in metadata.xml for 6 years but had

[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-22 Thread Matt Turner
On Fri, Jul 22, 2022 at 7:57 AM Joonas Niilola wrote: > > Cross-posting to gentoo-dev and -project lists due to technical and > non-technical nature. Reply-to is set to -project. > > Once again new council has been elected: congratulations to the chosen > members! And once again many nominees

[gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"

2022-07-22 Thread Alec Warner
On Fri, Jul 22, 2022 at 4:56 AM Joonas Niilola wrote: > > Cross-posting to gentoo-dev and -project lists due to technical and > non-technical nature. Reply-to is set to -project. > > Once again new council has been elected: congratulations to the chosen > members! And once again many nominees