[Mageia-webteam] Webteam peers, bootstrapping

[Romain d'Alverny]

Hi there,

we need to bootstrap the team organisation, so we can know especially
who is _in_ the team, can elect/be elected team
representative/leader/deputy leader, and vote for team formal
decisions (as well as having a base to dispatch some credentials, such
as having the production commit button, for instance). And start to
think about the mentoring process.

As suggested by misc during yesterday's meeting (notes:
http://meetbot.mageia.org/mageia-web/2011/mageia-web.2011-01-05-14.07.html
), I will, as "first fellow", name first peers. Here they are:

 * Oliver Burger (obgr): wiki, calendar, catdap
 * Kosmas Chatzimichalis (kosmas): maint-db
 * Toni Korpela (TMKCodes): secretary
 * Damien Lallement (damsweb): infra, blog, website
 * Buchan Milne (blingme): catdap
 * Olivier Thauvin (nanar): epoll
 * Samuel Verschelde (stormi): mageia-app-db
 * Pascal Villarem (maât): forum
 * Raphaël Jadot (ash): forum

Of course, as usual, I may have forgotten someone. So, the new peers
are welcome to suggest others if any.

I left some people out, who are especially active in other teams
(sysadm, marketing, artwork, packaging), follow the web team (and
that's good) but I'm not sure it's relevant to have a decisive voice
in the team's decisions; open for discussion.

(what is below is a draft)

What do peers have that non-peers do not?
 * they have a decisive voice in team decisions (they vote). Non-peers
have a consultative voice.
 * any peer can be elected representative to the Council, leader or
deputy leader.

After this first designation process is done, how to become a team peer?
 * you must demonstrate your constructive contributions to the team
work (patches, development, design insights, other); and your
understanding of the project's code of conduct
(http://mageia.org/en/about/code-of-conduct/ );
 * you must find a mentor (that is, an existing peer that recommends
you and mentors you for your first steps in the team); just ask;
 * your mentor proposes you to the team peers; and explain why (during
a meeting or on the list); should be short/quick/clear;
 * unless a significant number (?) of peers refuse, you're in.

This process can take from a few hours to a few months, depending on
you (already known, obvious contributions; or fresh new comer, no
active work yet). Of course, one can start contributing in many ways
before having a mentor and before applying.

What is mentoring here? explaining/demonstrating the whole Web setup,
a specific application, conventions, team processes. Validating the
apprentice work and that s/he can be a peer.

Here we are.

Cheers,

Romain