1 |
On 2006.08.27 22:37, Duncan wrote: |
2 |
> Roy Bamford <neddyseagoon@g.o> posted |
3 |
> 1156678084l.9833l.0l@spike, |
4 |
|
5 |
[snip] |
6 |
|
7 |
> |
8 |
> > If the council are to undertake the management of Gentoo, its terms |
9 |
> > of reference need to be drastically altered to allow them to |
10 |
> > undertake the management process defined above. |
11 |
> > |
12 |
> > In short, Gentoo has a top level power vacuum, allowing what |
13 |
> > amounts to the 'power struggle 'we see today. |
14 |
> |
15 |
> This is the best reading of the situation I've seen, IMO. Good work! |
16 |
> |
17 |
> Whether changing the rules to allow the council to manage |
18 |
> appropriately is politically doable or not remains an open question, |
19 |
> and I'm not even sure I'd back it myself if it is possible, but |
20 |
> that's the best description of where we are at that I've seen, which |
21 |
> means we've gone along way toward accomplishing the first step in any |
22 |
> good debate, a proper definition of the issue. |
23 |
> |
24 |
> -- |
25 |
> Duncan - List replies preferred. No HTML msgs. |
26 |
> "Every nonfree program has a lord, a master -- |
27 |
> and if you use the program, he is your master." Richard Stallman |
28 |
> |
29 |
> -- |
30 |
> gentoo-dev@g.o mailing list |
31 |
> |
32 |
> |
33 |
|
34 |
Changing the councils terms of reference is the easy bit. My |
35 |
understanding is that under the present rules, it needs a GLEP to be |
36 |
approved by the council, However, the rules only permit things to |
37 |
happen. In a volunteer organisation, management is a particularly |
38 |
thankless task, it can't be done with a carrot and a stick, the stick |
39 |
does just not exist and the carrot is a bit small too. |
40 |
|
41 |
Luckily 90% of management decisions can be purely arbitrary - all that |
42 |
matters is that a decision is made. In most of these cases, its fine to |
43 |
allow the recommendation from the teams to prevail, they will be doing |
44 |
the work after all. Its the other 10% that cause all the friction, |
45 |
where some individuals or group are going to be upset whatever decision |
46 |
is made. |
47 |
|
48 |
If the ruling body (Council ?) were a proactive planning body, rather |
49 |
than a reactive adjudication body, many of these things would we seen |
50 |
coming - they would not be the surprises they are today, which is what |
51 |
upsets protagonists. Planning is not really the councils job. |
52 |
|
53 |
I've just convinced myself that what's needed is a new Gentoo wide |
54 |
project - Gentoo Planning that takes input from all the teams as to |
55 |
what they want to do by when and collates it in an attempt to spot |
56 |
potential conflicts. Gentoo Planning can then alert the parties to |
57 |
allow a discussion to take place and refer any failures to agree to the |
58 |
council. |
59 |
|
60 |
Its more admin - and I hate admin ... but to trot out an old adage, |
61 |
"if you don't have a plan, then plan to fail" is very true. |
62 |
|
63 |
All this proposal amounts to is formalising the communications amongst |
64 |
the teams - maybe a gentoo-planning mailing list would be adequate, to |
65 |
which all teams posted plans and progress reports on a regular basis |
66 |
and which was compulsory reading. Regular being defined by each team |
67 |
from time to time, depending on planned activity. |
68 |
|
69 |
Maybe gentoo-planning is a devrel subproject, since its concernded ? |
70 |
|
71 |
Regards, |
72 |
|
73 |
Roy Bamford |
74 |
|
75 |
-- |
76 |
gentoo-dev@g.o mailing list |