1 |
On 22.7.2022 21.32, Robin H. Johnson wrote: |
2 |
> |
3 |
> BUT, we can't write a simple gitolite ACL that limits the content within |
4 |
> profiles/package.mask or other files in profiles/ (we can write hooks |
5 |
> that might be able to do this, but that still requires the challenge of |
6 |
> validation inside the file). |
7 |
> |
8 |
> I'd EXPECT a contributor to WANT to package.mask a cutting edge version |
9 |
> so it has time to bake and get well-tested, but if they can't do both |
10 |
> parts of the commit themselves, this process is likely problematic. |
11 |
|
12 |
Well as I said I think the best way is to fall back to the current way |
13 |
of a dev merging it, via Github PR or other means. I'd say pushing these |
14 |
experimental packages is rather rare (for proxied people at least), and |
15 |
can also be added without KEYWORDS for example. |
16 |
|
17 |
|
18 |
> |
19 |
> How do we make the mentorship process more lightweight? |
20 |
> (and possibly the quiz process, I haven't seen how the quiz has changed |
21 |
> since I last mentored) |
22 |
> |
23 |
> Let's start with a potential intersection of your two ideas: |
24 |
> (these numbers are arbitrary, but try to reflect what I see some of the |
25 |
> trusted contributors doing) |
26 |
> - 9 good submissions (patches or PRs) over a 3 month period [must be at least 3/month] |
27 |
> - will get you an invite from recruiters to join |
28 |
> - either without a mentor, or a lightweight mentor |
29 |
> |
30 |
|
31 |
This is a bit complicated topic and I'm not sure if I'm the best one to |
32 |
answer the mentoring part. But I'd like to point out this kind of |
33 |
teaching and/or "lighweight mentoring" happen everyday in |
34 |
#gentoo-dev-help, #gentoo-proxy-maint and in related IRC channels, and |
35 |
in Github PRs... just that it's done by multiple different people in |
36 |
different places. So many people add a little bit to one's growth |
37 |
instead of one/two people adding a lot, making weaker bonds with |
38 |
contributors. |
39 |
|
40 |
Then again I would say the entry bar is very high right now, which in |
41 |
return gives us high quality developers, but maybe less people are even |
42 |
interested in attempting it. With these propositions I guess we can |
43 |
focus less on the quiz, and more on the existing positive contributions |
44 |
and interactions when considering someone. |
45 |
|
46 |
So to help "lightweight mentoring": Grant some person you've been |
47 |
proxying commit access, follow their commits and their bugzilla |
48 |
activity, and after some time if you get good vibes from the person, |
49 |
encourage them to widen their contribution areas. If they manage it |
50 |
after a while, they have most likely accumulated enough experience and |
51 |
knowledge to get recruited. |
52 |
If you tell people to attempt the quiz after seeing 10 commits from |
53 |
them, and after they've been around for a month, it's most likely going |
54 |
to end up being a very long road for everyone involved. Please don't try |
55 |
to rush and force the quiz - if GOOD verbose answers come naturally, the |
56 |
person is most likely ready. |
57 |
|
58 |
As I was trying to present in the original post, this way of recruiting |
59 |
would be for someone who's been around for a long time already (+year) |
60 |
and has been actively contributing and participating in the community, |
61 |
keeping up with Gentoo's development changes. It's not for someone |
62 |
trying to rush their recruitment. So in your example, I _doubt_ we'd |
63 |
take the initiative. But then again, it's really about people who |
64 |
impress us and make us say "why hasn't this person been recruited |
65 |
already?" - there are no metrics we should even try to list here. |
66 |
|
67 |
-- juippis |