| 1 |
On Wed, 02 Aug 2006 12:00:56 +0200 |
| 2 |
Thierry Carrez <koon@g.o> wrote: |
| 3 |
|
| 4 |
> Excerpt from the metastructure model, chosen by the majority of devs |
| 5 |
> last year (and not my model): |
| 6 |
> [...] |
| 7 |
> * It may have one or many leads, and the leads are selected by the |
| 8 |
> members of the project. This selection must occur at least once every |
| 9 |
> 12 months, and may occur at any time. |
| 10 |
> [...] |
| 11 |
|
| 12 |
While we're on the subject of the metastructure model, could we |
| 13 |
consider changing this rule? It's a little strict, and I suspect it's |
| 14 |
honoured more in the breach than otherwise (by which I mean some, |
| 15 |
perhaps many, projects don't bother to hold a selection process every 12 |
| 16 |
months). The 12 month rule makes perfect sense for the council and |
| 17 |
foundation trustees but it's over the top as a rule for all |
| 18 |
projects. |
| 19 |
|
| 20 |
I would suggest something along the lines of, "selection of |
| 21 |
leadership of a project can occur at any time, but can be forced should |
| 22 |
a majority of the team feel a new selection is necessary", perhaps |
| 23 |
with a rider allowing projects to setup stricter rules if they feel the |
| 24 |
need. I'm assuming (since I haven't checked) that project membership |
| 25 |
requires agreement of the project (i.e. people can't just join a |
| 26 |
project without the existing project members' agreement). |
| 27 |
|
| 28 |
The idea being that if the current leadership want to step down they |
| 29 |
can do so and selection occurs within the project by default. At the |
| 30 |
other extreme, if a lead becomes a pita for everyone else on the |
| 31 |
project, the rest of the project can oust the lead by majority |
| 32 |
decision (hopefully a rare occurrence). |
| 33 |
|
| 34 |
-- |
| 35 |
Kevin F. Quinn |
Archives