1 |
On Sat, Nov 12, 2016 at 9:40 PM, William L. Thomson Jr. |
2 |
<wlt-ml@××××××.com> wrote: |
3 |
> On Saturday, November 12, 2016 9:16:09 PM EST Rich Freeman wrote: |
4 |
> |
5 |
>> What would you prefer that the Council spend their time on? The main |
6 |
>> purpose of the Council is to deal with cases where individual projects |
7 |
>> aren't able to resolve things on their own, conflicts between |
8 |
>> projects, and appeals from Comrel/QA. It is a democratically elected |
9 |
>> governance body. |
10 |
> |
11 |
> I am seriously in major shock at your statement. Coming from a Council |
12 |
> member... I think you have a complete misunderstanding of the purpose of the |
13 |
> Gentoo Council. I am flat out flabbergasted. |
14 |
|
15 |
My view of the purpose of Council is also something I've been |
16 |
completely up-front about in my various manifestos, for reasons I'll |
17 |
elaborate on. |
18 |
|
19 |
> |
20 |
> Things like that, ideas should be produced from Council members and set out as |
21 |
> the direction for Gentoo. Then motivate volunteers to help take Gentoo in said |
22 |
> direction. |
23 |
|
24 |
You don't need to be on the Council to come up with ideas for where to |
25 |
take Gentoo. That's basically the whole point of our meta-structure. |
26 |
|
27 |
If you want to make Java better, then just do it. You don't need to |
28 |
wait for the Council to have a vision for Java. If you have a vision |
29 |
for Java then run with it. If you run into some kind of conflict, |
30 |
then sure the Council can step in and try to tweak things so that |
31 |
everybody can maximize their contributions. |
32 |
|
33 |
Why do you think we have three different udev implementations? Do you |
34 |
think we'd be better off if the Council picked one and then told those |
35 |
who care about the others to go create a fork? The whole point of |
36 |
Gentoo is that we create choices for our users. |
37 |
|
38 |
The goal is to give everybody freedom to be leaders as much as |
39 |
possible, not to have developers sit around waiting for orders from on |
40 |
high. People contribute where they choose, not where somebody else |
41 |
thinks they should be contributing. If there aren't any Java packages |
42 |
in Gentoo it is because nobody thinks it is worth their time to invest |
43 |
in them, not because some leader said that people shouldn't be working |
44 |
on them. |
45 |
|
46 |
Now, sometimes people will have differing opinions on how something |
47 |
ought to be done and there is a need to set a global policy. |
48 |
Generally speaking the Council tries to take an approach of least |
49 |
interference in such cases, finding ways to enable everybody do |
50 |
accomplish their goals while giving way enough so that others can do |
51 |
so as well. How else do you think we became the only distro around |
52 |
where both Systemd and OpenRC are essentially first-class citizens, |
53 |
along with udev and eudev? |
54 |
|
55 |
You may see this as a lack of vision, but I see it as the opposite. |
56 |
THIS IS the vision. One where we can have leaders at all levels. |
57 |
|
58 |
And of course Council members lead initiatives. But the reality is |
59 |
that when we do it we're really just doing it in our capacity as |
60 |
individuals. Sometimes we decide something needs to be done and seek |
61 |
a volunteer among our ranks to try to lead it. However, if somebody |
62 |
who wasn't on the Council was seeking such a role we probably wouldn't |
63 |
hesitate to encourage them. I've been tinkering with a Copyright |
64 |
Policy which has come up recently, and I'll be giving it a bit more |
65 |
attention, but the reality is that others can of course contribute to |
66 |
it, or even try to take us in a different direction. |
67 |
|
68 |
And leadership is hardly limited to developers/etc. Those raising |
69 |
concerns with the Cormel process are essentially demonstrating |
70 |
leadership in doing so, and I think that this will lead to |
71 |
improvements. If most developers don't think they go far enough then |
72 |
they can elect others to take them further. |
73 |
|
74 |
If somebody finds themselves asking the question "why isn't somebody |
75 |
in leadership addressing foo?" then they should start by asking |
76 |
themselves "why aren't I addressing foo?" If you have an itch, |
77 |
scratch it! That's how just about everything gets done in the FOSS |
78 |
world, at least in community driven projects. |
79 |
|
80 |
-- |
81 |
Rich |