1 |
On Sun, Aug 08, 2010 at 11:18:03AM +0100, Ciaran McCreesh wrote: |
2 |
> On Sun, 8 Aug 2010 03:05:34 -0700 |
3 |
> Brian Harring <ferringb@×××××.com> wrote: |
4 |
> > > GLEP 55 *was* put up for a vote, along with GLEP 54, on 20090514. |
5 |
> > > GLEP 54 was accepted subject to GLEP 55 being approved. The vote on |
6 |
> > > GLEP 55 was a tie. |
7 |
> > |
8 |
> > A tie, with a decision to revisit next meeting- the next meeting it |
9 |
> > was decided that yes, g55 is addressing what can be considered a real |
10 |
> > issue. And in the 14 months since then, no one has requested it be |
11 |
> > voted on, or revisited. |
12 |
> |
13 |
> It's extremely misleading of you to claim that it's the responsibility |
14 |
> of the GLEP 55 authors to push it to the Council at this point. That |
15 |
> was already tried several times, and got nowhere. |
16 |
|
17 |
Whether you like it or not, it *is* the authors responsibility. |
18 |
If you want something passed/accepted it's ultimately your |
19 |
responsibility to see it through to the finish- even if the last |
20 |
council dropped it on the ground. |
21 |
|
22 |
Hopefully to make this clear so that this claim never shows up again, |
23 |
shit happens. The "request for topics" and "agenda" emails that are |
24 |
sent out are your chance to request council discussion, to point out |
25 |
that they dropped something, etc. Things don't always make it onto |
26 |
the council agenda- you keep pushing, refining the proposal, etc, till |
27 |
you get it in there. Like it or not, that's the system. |
28 |
|
29 |
If in doubt, I'll just point out that both mtime and REQUIRED_USE were |
30 |
dropped multiple months- pushing them forward I deemed worthwhile so I |
31 |
kept bringing it up till it made it into an agenda instead of |
32 |
silently dropped. |
33 |
|
34 |
Either way, those are your options- if you want something implemented, |
35 |
ultimately it's your responsibility to see it through. |
36 |
|
37 |
I'd strongly argue this applies beyond just the council- for PMS as an |
38 |
example, even if you manage to get something approved ultimately if |
39 |
you want it to move forward the implementation falls to your plate. |
40 |
Same thing goes for cvs/git, either you're reliant on other peoples |
41 |
time, or you contribute your own time to try and move it forward. |
42 |
|
43 |
For the Heinlein fans, TANSTAFL is appropriate. |
44 |
|
45 |
Either way, it's on the agenda. In the future ask for stuff to be |
46 |
readded if it falls off, saves a lot of grief in the process. |
47 |
|
48 |
~harring |