| 1 |
On Wed, Apr 7, 2010 at 4:30 PM, Richard Freeman <rich0@g.o> wrote: |
| 2 |
> Sure, it is the best way to make big changes |
| 3 |
|
| 4 |
Why then use anything else than the best tool when you can use the |
| 5 |
best tool? I didn't say that he should work on a GLEP though, but that |
| 6 |
he should "feel free" to do so, which is different. That meant that if |
| 7 |
he thought there was a point to it, was willing to do it, etc... |
| 8 |
|
| 9 |
Just a note about this. The council could for example make the |
| 10 |
decision to centralize all the documentation in a wiki, force the doc |
| 11 |
team to use tools they haven't chosen or even take that responsibility |
| 12 |
out of their hands. Basically step on their toes. Nice way to show |
| 13 |
respect for all the hard work they've done for years. Or this could be |
| 14 |
discussed on the relevant mailing-list(s) by everybody who feels |
| 15 |
concerned, input from the whole community (including the doc team) |
| 16 |
could be gathered, council members could chime in (I usually do), |
| 17 |
dissenting opinions could be documented, a consensus could be reached |
| 18 |
and then design decisions could be documented. See GLEP 1 for more |
| 19 |
information on that work flow. |
| 20 |
|
| 21 |
Gentoo has been driven by consensus since Daniel left, for better or |
| 22 |
for worse. You might not like this way to work, but that's OK. I |
| 23 |
didn't say I thought it was optimal either. All I know is I'm going by |
| 24 |
the book, but it allows me to rewrite some pages when I don't like |
| 25 |
them. The good news is that during the last meeting the council has |
| 26 |
decided to initiate an overhaul of GLEP 39. I'm still gathering |
| 27 |
material from various sources to start the discussions open to all |
| 28 |
users and developers. At that point you'll have the opportunity to |
| 29 |
suggest anything you think may improve the way the council works. |
| 30 |
|
| 31 |
> However, the council can |
| 32 |
> still show leadership in affirming their agreement on issues even if it |
| 33 |
> isn't a formal affair. |
| 34 |
|
| 35 |
We don't need a meeting for that. We can show leadership on the |
| 36 |
mailing-lists everyday. What do you think I'm doing right now for |
| 37 |
example? And by the way I don't believe that issuing a statement along |
| 38 |
the lines of "Yep, we agree" shows any leadership at all. |
| 39 |
Additionally, leadership is not about doing your job. You may want to |
| 40 |
peruse the council meeting logs and summaries for examples of |
| 41 |
leadership, and vote for real leaders next time if you think we suck. |
| 42 |
|
| 43 |
> I'm sure every other town government in the Western |
| 44 |
> World has taken a vote in support of their troops or something like that |
| 45 |
> without going through the official lawmaking process and all that - it is |
| 46 |
> just a gesture. |
| 47 |
|
| 48 |
We've been down that road many times before, but let me say it again: |
| 49 |
Gentoo is not a government, so any comparison to one is pointless. |
| 50 |
|
| 51 |
> I don't have the time to create such a website although I would agree that |
| 52 |
> it is sorely needed. Hence, I will try to be careful in throwing around |
| 53 |
> criticism - it is much easier to bring problems to the table than |
| 54 |
> solutions... |
| 55 |
|
| 56 |
Wise words, although constructive criticism is always welcome. In |
| 57 |
order to be really constructive however, criticism needs among other |
| 58 |
things to take into account goals, resources, history and rules. |
| 59 |
|
| 60 |
Denis. |
Archives