[gentoo-project] [RFC] Ebuild quizzes for existing developers

[Michał Górny]

Hello, everyone.

I'd like to discuss a proposal aiming to improve the general quality of
ebuilds in the Gentoo repository.


As most of you know (or at least suspect), ebuild quizzes are changing
over time.  New questions are added and existing questions are updated,
to cover for new EAPIs, policies or simply cover cases of common
mistakes.  This is all done so that new developers would be better
prepared to work on Gentoo, and would not repeat the same mistakes
as new developers before them did.  Besides, this extends the purpose of
quizzes into being a quick reference of all the stuff you should be
aware of before committing.

However, new quizzes apply only to new recruits.  Ideally, we assume
that existing developers learn of new EAPIs and new policies as they go,
and they've already made most of the mistakes and learned from them. 
However, this is not always true.  There are less-active developers,
there are people returning after long devaways, and sadly there are
cases when they do not try to learn new things but attempt to apply
obsolete standards and solutions.  Furthermore, some of the recruits
consider it unfair that they have to undergo harder quizzes than people
who joined Gentoo earlier.


What I'd like to propose are additional examinations similar to
the ebuild quiz, for existing developers.  They would be performed
as a joint QA/Recruiters effort, and they would aim to align
the level of examinations for all developers.  This would serve two
purposes.  Firstly, it would ensure that existing developers are fully
aware of the current EAPIs, policies, best practices and pitfalls. 
Secondly, it would align the rules and make sure that developers joining
earlier are not privileged compared to those joining later.

Of course, I'm not talking about requiring all developers to pass their
ebuild quizzes again.  The way I see it, we would be establishing a few
reference versions of quizzes, and comparing them to the current one. 
Then, for each version we would establish a smaller quiz specifically
focused on developers recruited at the time.  Naturally, the developers
recruited earlier would have to answer more questions while developers
recruited more recently would have less.

To avoid overburdening our teams and developers, the whole process would
be spread over time.  Every time the quizzes are prepared for the next
group of developers, they will be given 6 months to complete them
and arrange a review session.  As the examinations progress, quizzes for
next groups will be prepared.

If the developer in question fails to pass the examination in 6 months,
the developer's commit access will be revoked.  After 2 more months
without passing, the developer will be retired.


It is quite likely that before we will be able to finish
the examinations for all developers, the quizzes will change again. 
Naturally, the groups examined past that will have their quizzes aligned
to the newest version already.  The earlier groups will be subject to
further (even smaller) examinations once all groups are done for
the first time.  Eventually, we would be able to align all developers to
the same version of quizzes.

Once that is achieved, I'd like to keep quizzes in sync from now on. 
That is, whenever we add a new question we will pass it through
developers.  This will achieve a double goal.  Firstly, it will improve
ebuild skills of developers.  Secondly, it will provide additional
testing of new quiz questions before recruits end up having to answer
them.


What do you think?

-- 
Best regards,
Michał Górny