1 |
Yes, Gentoo is kinda democratic because the projects elect their own |
2 |
leads. |
3 |
|
4 |
Questions: |
5 |
|
6 |
1. How to handle superprojects that are themselves composed of |
7 |
subprojects and may or may not have their own non-project members? |
8 |
Should the subprojects get to vote? If so, do we just count the votes |
9 |
of each project's lead (probably elected bottom up), or all the |
10 |
project's members? |
11 |
|
12 |
2. If a project gets stagnant and "implodes into a ball of stiff stale |
13 |
tar" through complacency, should the gentoo developer community as a |
14 |
whole have veto power to be able to oust the lead? |
15 |
|
16 |
I'm kinda in favor of 2, just for the sake of keeping project leads |
17 |
accountable for making sure that the project exists to benefit gentoo |
18 |
as a whole. And it would work for any project that goes off course |
19 |
from the needs of the whole community...and not just "hot button" |
20 |
projects like comrel or whatever. |
21 |
|
22 |
IIRC we already have leads elected by the members of the project to |
23 |
have accountability to the project and the needs of its membres, but |
24 |
what about the accountability of the project to the gentoo community as |
25 |
a whole? |
26 |
|
27 |
Bosses and leads provide organization and structure and a clear path of |
28 |
responsibility. |
29 |
|
30 |
As for 1, I think that making a project part of another |
31 |
project...hmm...who decides that? |
32 |
|
33 |
On Wed, Oct 5, 2016 at 9:55 AM, Gregory Woodbury <redwolfe@×××××.com> |
34 |
wrote: |
35 |
> On Mon, Oct 3, 2016 at 6:16 PM, Raymond Jennings <shentino@×××××.com> |
36 |
> wrote: |
37 |
>> |
38 |
>> The only comment I have right now... |
39 |
>> |
40 |
>> What if project leads were generally left in charge to run their |
41 |
>> projects as they see fit, but the gentoo developer community as a |
42 |
>> whole reserved the right to recall the lead if they don't like how |
43 |
>> the project is being managed? |
44 |
>> |
45 |
>> This would help with stagnant projects or the like or projects (such |
46 |
>> as the recent fight between games and council) that aren't |
47 |
>> responsive to the needs of the gentoo community. |
48 |
>> |
49 |
>> I like democracy, but who should the voters be? |
50 |
>> |
51 |
> |
52 |
> Well, that is, to me, a large part of the problem. |
53 |
> |
54 |
> The social/political structure of Gentoo is based on a status of |
55 |
> being an "accredited developer." Meaning that there are hoops to jump |
56 |
> through to prove that one has a sufficiently advanced technical |
57 |
> ability, and an ability to work within the rules. This restriction on |
58 |
> who gets a vote or not makes the situation into one of conservative |
59 |
> vs. progressive: restricted voting rights are associated with |
60 |
> corporate |
61 |
> cultures that are inherently conservative. They are often more |
62 |
> concerned |
63 |
> with maintaining a "status quo" than in moving forward. |
64 |
> |
65 |
> This is *exactly* what and why these conversations are taking place |
66 |
> here and now. |
67 |
> |
68 |
> |
69 |
> -- |
70 |
> G.Wolfe Woodbury |
71 |
> redwolfe@×××××.com |