1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
2 |
Hash: SHA1
|
3 |
|
4 |
I am sometimes accused of "playing lawyer" when I get into discussions
|
5 |
like this. Curiously, I almost never play lawyer, and I pretty much
|
6 |
ignore such comments. So, warning: In this response, I am going to
|
7 |
play lawyer, look at the "B. Global issues ..." bit of GLEP 39, and
|
8 |
float an interpretation based on how I understand the intent. It might
|
9 |
provide a way to proceed, but it will also require Council to open its
|
10 |
sealed logs to some third party. Further comments in the proper spot
|
11 |
of the reply.
|
12 |
|
13 |
And as I repeat below, if ciaranm indicates that my reading is
|
14 |
incorrect, then I withdraw the argument which follows.
|
15 |
|
16 |
|
17 |
On Fri, 16 May 2008 23:38:42 +0000
|
18 |
Ferris McCormick <fmccor@g.o> wrote:
|
19 |
|
20 |
> -----BEGIN PGP SIGNED MESSAGE----- |
21 |
> Hash: SHA1 |
22 |
> |
23 |
> On Fri, 16 May 2008 18:39:03 -0400 |
24 |
> Richard Freeman <rich@××××××××××××××.net> wrote: |
25 |
> |
26 |
> > Ferris McCormick wrote: |
27 |
> > > And as I've said before, if we think a policy doesn't make sense, we |
28 |
> > > can change it. But changing a policy that affects Council and then |
29 |
> > > applying it retroactively gets tricky, because Council themselves are |
30 |
> > > part of the approval process. |
31 |
> > |
32 |
> > Nothing too tricky - council votes that the GLEP is to be modified |
33 |
> > retroactively. A few folks complain. Life goes on. |
34 |
> > |
35 |
> > > Changing policy is a fairly lengthy |
36 |
> > > procedure, but right now Council is on a one month clock to hold an |
37 |
> > > election unless something changes. It still seems to me that Petteri |
38 |
> > > has it right, and that it's better just to do it rather than talk about |
39 |
> > > it. |
40 |
> > > |
41 |
> > |
42 |
> > What happens if we just do nothing and pretend it didn't happen? Most |
43 |
> > likely, not much. |
44 |
> > |
45 |
> |
46 |
> We send the message to the community that policies don't much matter. |
47 |
> In this case, someone did bring up policy, so I don't see how we can |
48 |
> pretend it didn't happen. |
49 |
> |
50 |
|
51 |
<Lawyer Alert>
|
52 |
|
53 |
Let's look at "B. Global issues ..." and ciaranm's clarification of the
|
54 |
intent to see how we can interpret GLEP 39 in such a way as to satisfy
|
55 |
its intent without potentially forcing frequest Council elections and
|
56 |
without having to start tinkering with a pretty good policy statement.
|
57 |
I'm going to follow the international style and number my arguments,
|
58 |
and this is one of the few times you will see me play a lawyer. :) For
|
59 |
clarity, I letter my conclusions.
|
60 |
|
61 |
1. It is clear that if Council ever calls a meeting, anyone who
|
62 |
does not show up is marked absent and potentially a slacker;
|
63 |
2. Thus, no matter how anything else turns out, 3 or 4 Council members
|
64 |
might get slacker marks for missing the meeting called for 15.v.08.
|
65 |
3. The Council did schedule a meeting for 15.v.08 but never actually
|
66 |
did anything because it could not form a quorum.
|
67 |
4. On its face this looks like a violation of the 50% rule;
|
68 |
5. But the purpose of the 50% rule is to prevent some subset of the
|
69 |
Council from meeting and taking any sort of action (that is, if Council
|
70 |
ever do anything, they must have a quorum).
|
71 |
6. So we might argue that while it was pretty bad form for Council to
|
72 |
gather together a meeting on the 15th and then mostly not show up, they
|
73 |
didn't actually do anything so the intent of the 50% rule was not
|
74 |
violated.
|
75 |
- ---> I pass this on to ciaranm for a correct interpretation
|
76 |
because he knows the intent <---
|
77 |
7. If we read GLEP 39 like that, then this is not the end of the
|
78 |
story, because:
|
79 |
8. In the events leading up to the non-meeting of the 15th, it is
|
80 |
pretty clear that some number of Council members (a) did meet with
|
81 |
devrel lead one or more times, (b) in secret session(s), and (c)
|
82 |
*something* must have happened because as a result devrel lead took
|
83 |
action on complaint(s?) made directly to Council.
|
84 |
9. If at ANY of those sessions fewer that 50% of the Council were
|
85 |
present, then GLEP 39 most certainly was violated under the
|
86 |
interpretation in PPS 5, 6 (the ones which can get Council off the hook
|
87 |
for the 15th if we buy them).
|
88 |
10. Logs of those sessions are closed, however.
|
89 |
11. Thus, under one arguable reading of GLEP 39, we can have the
|
90 |
following:
|
91 |
|
92 |
A) For the 15.v.08 non-event, we have lots of absent members and as a
|
93 |
result might or might be forced to replace some Council members under
|
94 |
the slacker parts of GLEP 39.
|
95 |
B) Since the non-meeting of 15.v.08 didn't take any action except for
|
96 |
never starting, we can say that the 50% rule technically was not
|
97 |
violated;
|
98 |
C) But if we use that reading, then some number of "secret sessions"
|
99 |
of the Council most certainly did happen (if for no other reason, we
|
100 |
know this because devrel lead clarified policy and took action on
|
101 |
complaints which went directly to Council.)
|
102 |
D) If at *any* of these sessions fewer that 4 Council members were
|
103 |
present, GLEP 39 50% rule was violated in fact and in spirit.
|
104 |
E) Under this reading of GLEP 39, we must open all those logs to some
|
105 |
trusted members of the community (developers or not) who have no
|
106 |
connection to either devrel or Council for review.
|
107 |
F) If Council never met with fewer than 4 in attendance at these closed
|
108 |
sessions, we can probably finesse the open non-event of the 15th where
|
109 |
Council did nothing but annoy a lot of people.
|
110 |
G) If Council members did ever meet in private without a quorum, then
|
111 |
GLEP 39 is most certainly violated and we must replace Council;
|
112 |
H) If for some reason Council cannot or will not open those logs as in
|
113 |
E) then this entire argument must fail and we must replace Council for
|
114 |
the 15th. (Council do not get any White House executive privilege or
|
115 |
"missing emails" sort of pass. With this reading, "no records" ==
|
116 |
"violation and forced election.")
|
117 |
F) In other words, we can call the 15th a non-meeting for purposes of
|
118 |
GLEP 39 because nothing happened. But then all the closed sessions
|
119 |
leading up to the 15th must be treated as actual meetings because as a
|
120 |
result something did happen, and for them the quorum rule most
|
121 |
certainly does apply.
|
122 |
|
123 |
</end Lawyer Alert>
|
124 |
|
125 |
That's how I'd argue it so save Council from themselves for the 15th.
|
126 |
I could probably rearrange it and tighten it up, but that's me playing
|
127 |
lawyer. But it's all or none. You can't pick the parts you like and
|
128 |
ignore the rest.
|
129 |
|
130 |
Also, if ciaranm says my interpretation is incorrect, I defer to him as
|
131 |
the author of this policy and withdraw it.
|
132 |
|
133 |
For the record: I've never seen the logs. I have talked to some of
|
134 |
- --- --- -------
|
135 |
the players involved, but I have no idea at all if this approach would
|
136 |
force a Council election. And it could influence the discussion when
|
137 |
the non-meeting finally happens, because there will be non-players
|
138 |
around who will know all about events leading up to it.
|
139 |
|
140 |
> > Don't get me wrong - I'm not into dictatorships and I'm a big proponent |
141 |
> > of democracy. If most devs really want another election, then let's get |
142 |
> > it going. However, all of about 4-6 people (and not all devs) have |
143 |
> > chimed in on this discussion, which suggests that most don't care. If |
144 |
> > most devs don't care for a new election, wouldn't it just be a major |
145 |
> > distraction to call for an election now? You'll have three months of a |
146 |
> > lame-duck council and all kinds of decisions may get put off. |
147 |
> > |
148 |
> |
149 |
> Not really, because the clock resets. So the election is for 12 |
150 |
> months. That's pretty clear in the GLEP, I think. |
151 |
> |
152 |
> > A few posters in this thread have suggested that they'll probably vote |
153 |
> > for the exact same council, but it is just important that we follow the |
154 |
> > process. Hopefully none of these posters are among those accusing |
155 |
> > Gentoo of being bureaucratic - having an election just for the sake of |
156 |
> > having an election when most folks don't want a change just seems like |
157 |
> > an exercise in procedure. |
158 |
> > |
159 |
> > I'm just trying to be pragmatic - the council was democratically |
160 |
> > elected, and a new council will be elected in a few months. If the |
161 |
> > council just went and disappeared I could see the need for an emergency |
162 |
> > election to keep things going. However, at this point an election will |
163 |
> > just delay stuff getting done. |
164 |
> > |
165 |
> > I think that an election now would be a mistake. However, if we really |
166 |
> > want to survey the devs it wouldn't be a bad thing, although if anybody |
167 |
> > other than the few of us cared strongly they could just post here. If |
168 |
> > there really are a lot of devs who would like us to follow the letter of |
169 |
> > the current GLEP 39 then I'd be all for an election. |
170 |
> |
171 |
> Regards, |
172 |
> Ferris |
173 |
> - -- |
174 |
> Ferris McCormick (P44646, MI) <fmccor@g.o> |
175 |
> Developer, Gentoo Linux (Sparc, Devrel, Userrel, Trustees) |
176 |
> -----BEGIN PGP SIGNATURE----- |
177 |
> Version: GnuPG v2.0.9 (GNU/Linux) |
178 |
> |
179 |
> iEYEARECAAYFAkguGwkACgkQQa6M3+I///ciggCgkCqB/WFMB5v1z1H1SWrK8O1X |
180 |
> 8rEAn1BqjKgYyMJFxCiUIBoeUAJkU/l1 |
181 |
> =ydab |
182 |
> -----END PGP SIGNATURE----- |
183 |
> [Error decoding BASE64] |
184 |
|
185 |
Regards,
|
186 |
Ferris
|
187 |
- --
|
188 |
Ferris McCormick (P44646, MI) <fmccor@g.o>
|
189 |
Developer, Gentoo Linux (Sparc, Devrel, Userrel, Trustees)
|
190 |
-----BEGIN PGP SIGNATURE-----
|
191 |
Version: GnuPG v2.0.9 (GNU/Linux)
|
192 |
|
193 |
iEYEARECAAYFAkguoiEACgkQQa6M3+I///eeewCfc5npsCr+oc6hsbh5dksbMpso
|
194 |
CmQAoN27fEC4IjeBq7Z5uxLPUSt+GtSM
|
195 |
=dRBW
|
196 |
-----END PGP SIGNATURE----- |