1 |
On 06/18/2016 05:59 PM, Rich Freeman wrote: |
2 |
> On Sat, Jun 18, 2016 at 4:26 PM, Daniel Campbell <zlg@g.o> wrote: |
3 |
>> |
4 |
>> The less admin/bureaucratic overhead we have, the better. From what I |
5 |
>> gather even the Council feels this way, but that's just my two cents. |
6 |
>> |
7 |
> |
8 |
> ++ |
9 |
> |
10 |
> Certainly I feel this way. I'd say that most of m peers would agree. |
11 |
> Not that this ultimately matters since for the next two weeks the |
12 |
> final say in what the council should be really rests with the |
13 |
> developers. |
14 |
> |
15 |
> This topic has come up before. If you actually look at what powers |
16 |
> the council has in practice they are: |
17 |
> 1. Approve GLEPs. |
18 |
> 2. Appeals for comrel actions. |
19 |
> 3. Resolve disagreements within the community (such as between projects, etc). |
20 |
> |
21 |
> The ability for the council itself to actually get anything done is |
22 |
> purely dependent on how much its members want to spend their time |
23 |
> doing it themselves. The council doesn't actually have the power to |
24 |
> make anybody do anything. It does have the power to prevent somebody |
25 |
> from doing something, and to pick a side in a dispute to settle it. |
26 |
> For example, there was a dispute over how games should be managed, and |
27 |
> the Council decided that developers could form a new games project if |
28 |
> they wished, or maintain games outside of the project, and that it was |
29 |
> not necessary to use the games eclass or follow the previous games |
30 |
> project policies. What the Council can't actually do is force |
31 |
> somebody to go in and modify all the games ebuilds to stop using the |
32 |
> eclass. Maybe we could have all the games that use the eclass |
33 |
> treecleaned, but that would be like swatting a fly with a howitzer. |
34 |
> So, until somebody wants to actually implement the changes we're left |
35 |
> with the status quo. However, nobody is actually complaining about |
36 |
> the status quo, so it can't be that bad. Indeed, if somebody thought |
37 |
> it was bad, they'd just fix it, and with the council decisions in hand |
38 |
> nobody could interfere with their work. |
39 |
> |
40 |
> Ultimately that is the practical role of the council. If there is |
41 |
> something you want to do in Gentoo, then DO IT. And if somebody gets |
42 |
> in your way, the Council can get them out of your way, or help find a |
43 |
> middle way that lets everybody accomplish their goals. |
44 |
> |
45 |
> When it comes down to actually leading initiatives, well, we already |
46 |
> have GLEP 39 which basically says that anybody can do it. You don't |
47 |
> need to be on the Council to make a big project happen. You just need |
48 |
> to appeal to devs to contribute. If your appeal falls on deaf ears, |
49 |
> trust me, being on the council isn't going to make it go any better. |
50 |
> To the degree that any of us have sway in the community we had it |
51 |
> before we ever joined the council, and maintain it apart from our |
52 |
> participation in the council. |
53 |
> |
54 |
> Now, if you view the Council as a badge of honor or something to be |
55 |
> put on a resume, then I certainly can understand frustration when |
56 |
> people with low commit rates/etc or low rates of making big proposals |
57 |
> aren't on the Council. However, if you view the role of the Council |
58 |
> as running interference for the people who really are getting the work |
59 |
> done, then you might appreciate that it isn't always beneficial to |
60 |
> have the Council buried in implementing portage enhancements or |
61 |
> whatever. Often "calmer heads" is one of the more important |
62 |
> attributes, as well as technical competence. |
63 |
> |
64 |
> Oh, and a willingness to write up meeting summaries never hurts. :) |
65 |
> |
66 |
Thanks for the thorough explanation; my thoughts were pretty much right |
67 |
in line with that, and I think it's for the better. It gives 'power' to |
68 |
those who want to do the work or are willing to come up with workable |
69 |
solutions that suit most or all people involved. |
70 |
|
71 |
A great example is the recent USE_EXPAND="gui" or L10N. Some people want |
72 |
these changes to happen, but are tackling real world problems at the |
73 |
same time as some bike-shedding so that the ideas can build and evolve |
74 |
into something suitable. I think some view situations like those as |
75 |
make-it-or-break-it deals, and perhaps that stalls discussions and |
76 |
steers them in less-productive directions. It's my hope that the council |
77 |
doesn't need to get involved, because the entire consequence of |
78 |
collaboration is we're going to have to find practical solutions that |
79 |
fix as many issues for as many people possible without taking away |
80 |
options. Few distros can do that; the ones who can are mostly based on |
81 |
Gentoo in the first place. |
82 |
|
83 |
So I guess maybe our protracted discussions and "slowness" is a good thing. |
84 |
|
85 |
-- |
86 |
Daniel Campbell - Gentoo Developer |
87 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
88 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |