1 |
Dean Stephens: |
2 |
> On 12/30/14 09:25, hasufell wrote: |
3 |
>> Dean Stephens: |
4 |
>>> On 12/29/14 15:06, Rich Freeman wrote: |
5 |
>>>> I'll certainly agree that not everything needs a formal project. |
6 |
>>>> However, if a project wants to have authority/autonomy beyond |
7 |
>>>> anything-goes, then it should welcome members and elect a lead |
8 |
>>>> regularly. |
9 |
>>>> |
10 |
>>> There is at least a defensible argument to be made that being able to |
11 |
>>> reject applicants is more important to being able to maintain a coherent |
12 |
>>> project than the often indicated duty to accept anyone who shows interest. |
13 |
>>> |
14 |
>> |
15 |
>> What about projects that don't even reject, but rather ignore |
16 |
>> devs/contributors? |
17 |
>> |
18 |
> If they have a maintained project page, have elected a lead in the past |
19 |
> 12 months, and that lead is otherwise active; take it for what it is: |
20 |
> rejection [1]. Otherwise, they either need to elect a new lead or allow |
21 |
> the project to dissolve, according to GLEP 39 [2]. |
22 |
> |
23 |
>> We tell them to elect a new lead, so we don't have to deal with the |
24 |
>> people who screwed up, but can say "here, they formally are a functional |
25 |
>> project according to a random glep... problem solved". |
26 |
>> |
27 |
>> |
28 |
> So, the document specifying the organizational structure of Gentoo as a |
29 |
> whole [2, again] is just "a random glep" now? Is anyone supposed to take |
30 |
> that rhetoric seriously or were you attempting to use humor? Either make |
31 |
> a concrete proposal to update or entirely supersede the existing project |
32 |
> structure or work within it, merely complaining about it is pointless. |
33 |
> |
34 |
|
35 |
You did not get the point. The point is that the problem is not the GLEP |
36 |
in the first place. By forging just the GLEP, you will not get the |
37 |
problem solved. |
38 |
|
39 |
And I have been very specific indeed. |