1 |
Alistair Bush wrote: |
2 |
> It really isn't the Councils decision and the only thing they can do to |
3 |
> get themselves out of this situation is to hold an election. Firstly, |
4 |
> even tho this is absolutely minor , GLEP 39 has been "breached" and it |
5 |
> details what the solution is for that breach. Therefore that solution, |
6 |
> a new council via an election, _must_ be performed. |
7 |
> |
8 |
|
9 |
Uh - the word "must" is a bit strong. Why "must" an election be |
10 |
performed? GLEP 39 is a document several years old, that probably |
11 |
pre-dates half of the devs here, and most likely most of the ones that |
12 |
were around weren't really envisioning that it be used in this way today. |
13 |
|
14 |
> If it isn't then we will no longer have a functioning Council with a |
15 |
> mandate from the ppl!!! ( maybe a little over dramatic ). There would |
16 |
> be no requirement for anything they say to be enacted upon and the "shit |
17 |
> would hit the fan". ( or would we just elect a new council and let them |
18 |
> pretend to be the one true Council ). |
19 |
|
20 |
First - I suspect that most devs don't really care a great deal about |
21 |
this issue - I doubt that the hundred-or-so required devs to fork a new |
22 |
distro are going to leave because a few people missed a scheduled |
23 |
meeting. If the council announced that there would be a re-do of the |
24 |
meeting and a new discussion of GLEP 39 I doubt that people would start |
25 |
ignoring the resolutions of the council - particular those in key roles |
26 |
in the project (ie those with administrative access to project |
27 |
resources, the trustees, etc). If the council announced new elections |
28 |
then everybody would start working towards new elections. |
29 |
|
30 |
The council was elected because they already had the respect of most |
31 |
gentoo devs. That isn't going to change simply because a few people |
32 |
missed a meeting. Organizations aren't run by job titles unless those |
33 |
job titles come with the ability to sign paychecks. They're run by |
34 |
people - and leadership is respected regardless of policies written on |
35 |
paper. |
36 |
|
37 |
> |
38 |
> Could any developer challenge the validity of the Council. Who would be |
39 |
> responsible for judging that, Foundation members? |
40 |
|
41 |
Anybody can do anything they want - most of us live in free countries. |
42 |
Who would judge that? Well, that would be our peers. When we say |
43 |
stupid things people start ignoring us. When we say smart things people |
44 |
listen to us. I can post a poll on some forum somewhere and call it a |
45 |
gentoo election, but nobody is going to pay attention to the results |
46 |
because most people wouldn't recognize me as a gentoo leader. If a |
47 |
bunch of well-respected devs did the same thing then there is a good |
48 |
chance everybody else would go along with it (or there would be a fork). |
49 |
However, I don't think all that many well-respected devs are eager to |
50 |
mount a coup over a single missed meeting. |
51 |
|
52 |
> |
53 |
> In fact, whose duty is it too call the election? Decide when any |
54 |
> election is to take place? |
55 |
|
56 |
Hmm - I suspect that would again be the council - since everybody |
57 |
already looks to them for leadership. Why don't we see what their |
58 |
perspective is? If you feel strongly about new elections try contacting |
59 |
one of them directly and talking about it. Most council members have |
60 |
gotten where they are because folks think they have a good head on their |
61 |
shoulders - they're likely to listen to you. If they hear lots of |
62 |
people calling for a new election I suspect that they'd go ahead and |
63 |
hold one. I think that those who are concerned about this issue would |
64 |
get further in this way than by kicking up a storm on a mailing list |
65 |
(not that open discussion is a bad thing). Don't be surprised if they |
66 |
don't take action on the basis of one communication, but if they hear |
67 |
from lots of devs they'd probably take it seriously. |
68 |
-- |
69 |
gentoo-project@l.g.o mailing list |