[Mageia-discuss] Mageia governance model draft

Wed Oct 6 00:44:06 CEST 2010

On Tue, Oct 5, 2010 at 20:42, Oliver Burger <oliver.bgr at googlemail.com> wrote:
+> "Romain d'Alverny" <rdalverny at gmail.com> schrieb am 2010-10-05
+>> Apprentices have no voice yet and less rights on infrastructure,
+>> provided they are being mentored. It's then up to Masters to decide if
+>> an Apprentice makes it to Master or not. That's the reality behind the
+>> mentoring process.
+>
+> In technical things I support two or more levels. There's much to learn for
+> little community packagers as myself as there is in any field for the
+> newcommers.
+> As you describe it, there will be a political division in oldtimers with the
+> power to vote and newcommers without it as well. And this I can't support.
+> This sounds too much like a group of oldtimers hanging on to their power (even
+> if it is not, and I really do believe in you trying to be as democratic as
+> possible).
+>
+> Please don't initiate any kind of caste-system, to be as open as possible we
+> do need a hirarchie as flat as possible.
+
+I understand your fear and maybe words were not the right ones or it
+was not clearly explained enough.
+
+It's not a caste. It's encouraged that team do listen to everyone
+involved with them, no matter who (and people may be involved in
+several teams, indeed).
+
+But in last resort, not only involved, but committed people get a
+decisive voice. In teams, those committed people are those who were
+recognized as such by their peers, through the mentoring process.
+
+Which process is not an exclusive one (keep "bad" newcomers out), but
+an inclusive one (welcome and train them before they get full hands on
+the infrastructure). And that, again, wouldn't prevent non-'masters'
+and 'non-apprentices' to provide/contribute something to the project,
+only should it be reviewed and committed to the project by those team
+members.
+
+Does this answer somehow your point or not?
+
+Cheers,
+
+Romain
+