[Mageia-discuss] Mageia governance model draft
ahmadsamir3891 at gmail.com
Tue Oct 5 18:10:23 CEST 2010
On 5 October 2010 17:48, Tux99 <tux99-mga at uridium.org> wrote:
> On Tue, 5 Oct 2010, Romain d'Alverny wrote:
>> Teams are made of at least two sub-groups (from a credentials point of view):
>> * "Apprentices" (people being mentored into the team - someone
>> suggested "petit scarabée" as a label but...)
>> * and "Masters".
> Romain, that sound like a very rigid regimented structure that I fear
> will cause "i'm better than you" kind of feelings, etc.
> I don't see the point in strictly classifying people in either masters
> or slaves (sorry, freudian slip, i meant apprentices) because skill
> levels are a lot more varied and fluid than just two classes.
> Of course there will be mentors and mentored but there is no need to
> create a rigid two class structure with priviledges for the master
> This sounds very much against the spirit of a collaborative community to
> Please also read my other related post:
> I hope this dual-class system is not set in stone already.
It's not about skill, it's about experience, any packager who's going
to gain commit/submit privileges to the official repos needs to be
clued in on how that system works, what packaging rules to follow,
what's to avoid... etc; some how like the mailing lists etiquette
users, who were posting to mailing lists for the very first time,
needed to learn. The difference here is submitting a package in the
repos means many users may use it, so stricter rules apply here.
And the apprenticeship won't take a year, probably about 1 month (2 at
the very most), depending on each mentors' time. Collaborating means
new comers should be taught on how that they collaborating in should
FWIW, most of the packagers who maintained packages in Mandriva went
through the same teaching/apprenticeship process.
“Reminds me of Star Wars, 'Apprentice' does” :)
More information about the Mageia-discuss