1 |
Zeerak Mustafa Waseem wrote: |
2 |
> But isn't it the councils purpose to lead gentoo? |
3 |
|
4 |
It's my understanding that council gets elected to lead gentoo as a |
5 |
whole. But in the end the one doing the work gets to decide what's going |
6 |
on (as long as it's intra-project; the only thing i remember where |
7 |
council got to vote on a "project" outcome is PMS/EAPI) |
8 |
|
9 |
Don't get me wrong: several times i hoped for somebody with authority to |
10 |
magically end discussions on an issue, handing out the right direction |
11 |
and be done with it (you already mentioned python-3). |
12 |
But in a "consensus" community like gentoo we will instantly have |
13 |
discussions about "our" definition of "right direction". Only a select |
14 |
few still have that authority required to end a sub-thread with their |
15 |
"right direction". And this is mostly because they post hard facts you |
16 |
are buying because they've done so for years and otherwise kept their |
17 |
mouth shut. |
18 |
|
19 |
But i disgress.. |
20 |
|
21 |
> By leading they have to either delegate to someone to supervise |
22 |
> Gentoo projects or do it themselves. |
23 |
|
24 |
No. It just doesn't work that way. GLEP39 says projects may have a |
25 |
leader, who will hopefully be responsible to the projects members. |
26 |
|
27 |
That's the person you want to turn to. Older projects may still have a |
28 |
"operation" lead and a "strategic" lead. In that case, you want the |
29 |
"strategic" lead :) |
30 |
|
31 |
The whole wording and history of the GLEP gives projects most of the |
32 |
power. They can't be blocked by the community, they can conflict, they |
33 |
can go defunct at any time. All these are explicitly spelled out in the |
34 |
GLEP. |
35 |
|
36 |
> I do agree |
37 |
> that doing something yourself will always be the first step, but |
38 |
> there is no way every developer can keep track of everything that's |
39 |
> going on. |
40 |
|
41 |
They are not required to. I'm not required to know of the wiki project |
42 |
or the huge issue that python3 going stable seems to be. My |
43 |
responsibility as a dev is to keep up with things I work on, like EAPI |
44 |
changes. If I *want* others to notice, I'll contact council (if I need a |
45 |
decision) or PR (if I have an announcement). |
46 |
|
47 |
You are proposing a centralized solution. This hasn't worked since |
48 |
Daniel left and I personally think gentoo's too large to successfully |
49 |
try it again. |
50 |
|
51 |
> I utterly fail to see why there should be any rock throwing. |
52 |
|
53 |
Me too. But it happens. Despite a dozen folks calling for calm again and |
54 |
again. I don't want to offer explanations for it, this mail has gotten |
55 |
long enough as it is ;) |