From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-project@lists.gentoo.org
Cc: Joonas Niilola <juippis@gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-project] RFC: "Trusted contributor model"
Date: Sat, 23 Jul 2022 12:35:15 +0200 [thread overview]
Message-ID: <2836251.e9J7NaK4W3@pinacolada> (raw)
In-Reply-To: <8b133b01-58a2-788d-3f6e-c12e4a71f4db@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
>
> 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 developers? And currently I'm talking about people who have
> been active for a very long time (+year or two), who keep up with
> development-wise changes in Gentoo (eclasses, EAPI, virtuals...),
> participate in the community, and always provide top-quality
> contributions, but for some reason never got a mentor? I'd like to point
> out that this method would only be for the very few ones and recruiting
> through mentoring would still be the desired method.
> Recruiting through
> recruiters would still require the candidate to fill the
> ebuild/developer quiz, and they'd have to pass it without a mentor. So
> I'll emphasize: Currently only few special ones would qualify.
These who would fit here are the people where mentoring takes literally
no effort. So someone could be mentor in name - which would also have
the advantage that the future developer has someone to talk to if there
are any problems or questions.
I dont think this actually brings an improvement.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2022-07-23 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 11:56 [gentoo-dev] RFC: "Trusted contributor model" Joonas Niilola
2022-07-22 15:17 ` [gentoo-dev] Re: [gentoo-project] " Alec Warner
2022-07-22 18:18 ` Matt Turner
2022-07-22 18:30 ` Joonas Niilola
2022-07-26 20:31 ` Zoltan Puskas
2022-07-22 18:32 ` Robin H. Johnson
2022-07-22 19:10 ` Joonas Niilola
2022-07-26 23:39 ` Martin Dummer
2022-07-23 10:35 ` Andreas K. Huettel [this message]
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=2836251.e9J7NaK4W3@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=juippis@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