1 |
On Sunday, January 15, 2017 9:28:17 PM JST, Rich Freeman wrote: |
2 |
> On Sun, Jan 15, 2017 at 4:10 AM, Ulrich Mueller <ulm@g.o> wrote: |
3 |
>>>>>>> On Sat, 14 Jan 2017, Doug Freed wrote: |
4 |
>> |
5 |
>>> Therefore, I'm specifically asking the council to remove the |
6 |
>>> ambiguity in the language and pick one clear meaning. |
7 |
>> |
8 |
>> The council has no jurisdiction over GLEP 39 and cannot change its |
9 |
>> wording. GLEP 39 defines our metastructure, including the council |
10 |
>> itself, and was approved by an all devs vote. |
11 |
>> |
12 |
> |
13 |
> While this thought did occur to me, the topic seems trivial enough |
14 |
> that it would be silly to have a constitutional crisis over it. All |
15 |
> the deliberations over the Trustees/Council/SPI stuff might fall into |
16 |
> that category, but what to do over projects that lack a lead? |
17 |
> |
18 |
> And if we did decide that we don't want to touch it, that basically |
19 |
> leaves us in a de facto situation where projects don't need to elect a |
20 |
|
21 |
So, I am not quite sure what you mean by whether the council gets to |
22 |
"decide" if they want to touch the topic or not. You don't really have a |
23 |
choice in the matter. Ulrich's facts were quite clear. |
24 |
|
25 |
Are you under the delusion that you and the council get to choose such |
26 |
things? |
27 |
|
28 |
It seems the developer community at large may need to revisit and vote on |
29 |
such a change for GLEP39. Assuming it is deemed important enough to |
30 |
pursue. |
31 |
|
32 |
> lead, since GLEP39 did not make any provisions for enforcing that |
33 |
> requirement, and heaven forbid somebody take the initiative to come up |
34 |
> with one because GLEP39... :) |
35 |
> |
36 |
> However, I don't think we need to revise GLEP39 so much as point out |
37 |
> how it has been working in practice, comment on it, or clarify its |
38 |
> meaning. I suppose if somebody else takes strong objection they can |
39 |
> lead the constitutional rebellion. :) |
40 |
> |