Hi everyone, so, back in October, we presented you with the governance model for Mageia: - teams with members, among which elected leaders and representative, - a council of representative, - a board of elected past representatives.
At the time, we did not agree on, or find, a way to manage how contributors (with a consultative voice) would become full team members (with a decisive voice in the team). We had a debate about the wording in the mentoring process too (the "master" thing). So we just left some time to think about it. Remember, the governance is (basically) based on a bottom-up structure where contributors get mentored into the teams (become team peers), elect their representative to the Council (managing projects day-to-day life), which in turn elects the Board (which sets the project direction and manages the association). Back to teams. Having to bootstrap things now (that is, having some ground to have leaders and representatives), we tried to come up locally with something working first before exposing it; hence this mail, to share the experience and get some feedback. Packaging/devs teams did it lately, see https://mageia.org/pipermail/mageia-dev/20101217/001751.html . Team peers (who could elect or be elected) were designated as those who were already official Mandriva packagers in the past. So, they elected two representatives that will share the leader/representative roles. These were elected for 6 months by all packagers registered on the packagers wiki page. In turn, these representatives will have to coordinate the mentoring process setup. Web team did it too, with a slightly different process, having no real reference for "previous official Mandriva packagers". The process has been described/applied in this mail after the Web team meeting past week: https://mageia.org/pipermail/mageia-webteam/2011-January/000093.html . I'll make it short and just ask for your feedback about this and see how we can make a more generic pattern for each teams, flexible and simple enough. Cheers, Romain
