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

[Joonas Niilola]

On 22.7.2022 18.17, Alec Warner wrote:
>
> Who decides which contributor gets access to which package?

I imagine the person / project who has been proxying them until that
point. Even if the contributor gets a special access to a single
package, you'd still have a @gentoo.org maintainer proxying - if there's
an increasing amount of bug reports and poor work after commit access is
given, this proxy sees it and can request removal of access and start
teaching the contributor through reviews again. I'm aware there could be
some lazy people requesting it immediately, but let's think of the
positives and not paint it black quite yet.


> Is there a flow to eventually onboard contributors as developers?

It'd help combined with my 2nd RFC of the original post, yes. But I
believe some contributors would be fine with this arrangement too, where
they get to keep package(s) of their interest in a good condition
without having to tackle the quiz.

Anyway I only see positives for someone on the road of becoming a
developer with this approach.


> Why are the contributors not developers themselves, just with scoped
> ::gentoo access?
>

Remind me again, didn't we do this with arch testers historically? And
how did that work out? (This isn't a negative tone, genuinely asking
YOUR perspective)

I wouldn't mind this at all, but in a way I guess we'll want to identify
people who a) have passed the quiz & interview, b) has full tree access.

-- juippis