1 |
On Fri, Apr 17, 2015 at 7:30 PM, Kent Fredric <kentfredric@×××××.com> wrote: |
2 |
> |
3 |
> The best argument I have for why the quizzes being what they are is they |
4 |
> require you to engage with gentoo staff in order to get them answered, and |
5 |
> thus ensure you know how to ask questions. |
6 |
> |
7 |
|
8 |
That, and that you're able to interact with other developers, and know |
9 |
WHEN to ask questions. |
10 |
|
11 |
I'll take somebody who knows they can't write an ebuild and thus |
12 |
doesn't commit anything without getting it reviewed over somebody who |
13 |
think's they're God's gift to Gentoo and runs scripts that tweak half |
14 |
the tree without so much as a whisper on -dev in advance. The quizzes |
15 |
really are just a basic competency test combined with an interviewing |
16 |
tool. The recruiters need to assess responsibility/maturity, |
17 |
communication skills, and understanding of the fundamentals. Anybody |
18 |
can read the devmanual to brush up on some detail they forget. What |
19 |
we really need is somebody who realizes that they SHOULD read the |
20 |
devmanual. |
21 |
|
22 |
I'm not dismissing technical competence, especially the fundamentals. |
23 |
It just isn't the area that tends to actually get us in trouble. |
24 |
|
25 |
And if we did go with a more review-oriented workflow, it would |
26 |
actually increase the importance of the soft skills. A reviewer isn't |
27 |
just ensuring that libfoo builds - they're also coordinating with all |
28 |
the reverse dependency maintainers to ensure that they don't just |
29 |
break without warning. |
30 |
|
31 |
Look at it another way. I and just about everybody else with an @g.o |
32 |
address on this list basically has root access to every Gentoo box you |
33 |
use (unless you have your own rigorous QA process). You're putting a |
34 |
lot of trust in us. We owe it to you to ensure that somebody who is |
35 |
going to get upset and stick something nasty in an ebuild because |
36 |
they're having a bad day doesn't have commit rights. |
37 |
|
38 |
There are plenty of flame wars on the lists, and many differences of |
39 |
opinion. However, when it comes to the repository we really don't |
40 |
have much tolerance for messing around. Things like revert wars or |
41 |
reverts of QA commits need to be treated very seriously. |
42 |
|
43 |
So, that is part of why we have mentors/recruiters/interviews/etc. |
44 |
We'd like to get to know you. |
45 |
|
46 |
-- |
47 |
Rich |