From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: "Trusted contributor model"
Date: Sat, 23 Jul 2022 07:47:21 +0300 [thread overview]
Message-ID: <f5e826f2-addb-f0b7-84a4-8b226de53d8f@gentoo.org> (raw)
In-Reply-To: <B5KZKPZQ.5JNKGTAA.LLONTYBL@TEOFJW24.ZZQUYIDC.SX7DEB7R>
[-- Attachment #1.1: Type: text/plain, Size: 2116 bytes --]
On 22.7.2022 22.53, Roy Bamford wrote:
>
> Try it and see.
> Once access had been granted. Who is responsible for monitoring?
> I would expect it to be the dev that usually made the commits but
> due to the trust model, more or a random sample basis.
Yes, a @gentoo.org person/project is still required to be listed as a
maintainer, and they take responsibility.
I imagine anyone can ask for the access to be revoked if they see the
committing person causing more harm than good, and if there's a conflict
between devs then QA can decide.
>
> Are these trusted contributors devs?
> e.g. accounts on Woodpecker, standing/voting in council elections
> and so on?
No. If my feeling how-to-make-this-work is correct, there's no need to
setup an LDAP account for them.
>
> I'm more on the fence on this one. The mentors job does not stop
> when recruitments completes. The mentor is still required to keep a
> weather eye on progress for another six months.
>
> How does the post recruitment mentoring happen with no mentor?
> I can see how it works with the subjects in RFQ 1 ... they have
> been mentored since they obtained their trusted status but what
> about others?
>
Mentor is _required_ to monitor their mentee _one_ month after
recruitment. But I think I get what you mean, there's not that intimate
relationship anymore.
Even now at least me and gokturk have a habit of giving some general
feedback to the new recruit after one month, which requires checking
what they've done during that time. But really, #gentoo-dev in general
is very helpful and I got to give credit to sam who always seems to be
the first one on spot when a new recruit is having some questions. I
guess in a way we'd be sharing the "mentoring load" between multiple
people instead of focusing one one giving all support.
And again, we wouldn't recruit "just anyone" with this method, but the
people who've proven they got it. I'm not too worried about this. But
remember people, there's no shame in asking before doing something
potentially breaking!
-- juippis
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2022-07-23 4:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 11:56 [gentoo-project] RFC: "Trusted contributor model" Joonas Niilola
2022-07-22 15:17 ` Alec Warner
2022-07-22 17:53 ` Joonas Niilola
2022-07-22 19:54 ` Alec Warner
2022-07-23 5:02 ` Joonas Niilola
2022-07-22 18:18 ` Matt Turner
2022-07-22 18:30 ` Joonas Niilola
2022-07-22 18:32 ` Robin H. Johnson
2022-07-22 19:10 ` Joonas Niilola
2022-07-22 20:51 ` John Helmert III
2022-07-22 19:53 ` Roy Bamford
2022-07-23 4:47 ` Joonas Niilola [this message]
2022-07-23 10:35 ` Andreas K. Huettel
2022-07-23 10:37 ` Andreas K. Huettel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f5e826f2-addb-f0b7-84a4-8b226de53d8f@gentoo.org \
--to=juippis@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox