1 |
On 04-08-2011 13:08:06 -0700, Donnie Berkholz wrote: |
2 |
> On 18:15 Tue 02 Aug , Fabian Groffen wrote: |
3 |
> > > > Right, which means to me that if the council agrees on a certain change |
4 |
> > > > to GLEP39, it has to organise a full developer vote with all the |
5 |
> > > > supporting material for the change. |
6 |
> > > |
7 |
> > > But, you are saying that the council has to approve changes for glep |
8 |
> > > 39 before they can come to a vote. This would mean that say a majority |
9 |
> > > of developers doesn't like something in glep 39, but the council |
10 |
> > > doesn't approve the change. That change will never come to a vote. In |
11 |
> > > other words, the council has control of the rules that govern it. Is |
12 |
> > > that what you are intending? |
13 |
> > |
14 |
> > I think yes, if the council regarding GLEP39 thinks A, but the dev |
15 |
> > population B, then it is unlikely the council will vote for B. However, |
16 |
> > the dev population should vote for other council members that do support |
17 |
> > B for the next term in that case. |
18 |
> |
19 |
> I think the whole idea is rather absurd that the council could disagree |
20 |
> with a change to GLEP 39 and thus prevent it from going to a |
21 |
> developer-wide vote, even though they don't think they have the |
22 |
> authority to change the GLEP. |
23 |
|
24 |
Let me try to put it different: |
25 |
|
26 |
The assumption that the council has to vote for GLEP39, perhaps is |
27 |
wrong. Would it make more sense when the council would suggest the |
28 |
changes for GLEP39 and have the dev community vote on acceptance? |
29 |
|
30 |
Beforehand, the council then -- internally -- has to vote if they agree |
31 |
on the changes being put forward to the dev community. I think there |
32 |
should be a majority vote among the council members before such proposal |
33 |
is sent out for a dev vote. |
34 |
|
35 |
|
36 |
-- |
37 |
Fabian Groffen |
38 |
Gentoo on a different level |