1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 10/15/2013 11:00 PM, Markos Chandras wrote: |
5 |
> On 10/15/2013 09:53 PM, hasufell wrote: |
6 |
>> On 10/15/2013 10:46 PM, Markos Chandras wrote: |
7 |
>>> On 10/15/2013 09:40 PM, hasufell wrote: |
8 |
>>>> On 10/15/2013 10:28 PM, Markos Chandras wrote: |
9 |
>>>>> On 10/15/2013 09:16 PM, hasufell wrote: |
10 |
>>>>>> I wonder if undertakers should also check for inactive |
11 |
>>>>>> project leaders/members and remove them from the |
12 |
>>>>>> projects in case there has not been any activity for a |
13 |
>>>>>> while, regardless of the internal project structure. |
14 |
>>>>> |
15 |
>>>>>> Authority does not only come with knowledge, but also |
16 |
>>>>>> with commitment. |
17 |
>>>>> |
18 |
>>>>>> If no one disagrees, then we should add this to the list |
19 |
>>>>>> of undertakers competence. |
20 |
>>>>> |
21 |
>>>>> |
22 |
>>>>> We already check for inactive members (developers and |
23 |
>>>>> leaders are the same for us) |
24 |
>>>>> |
25 |
>>>>> What's is this thread for? |
26 |
>>>>> |
27 |
>>>>> |
28 |
> |
29 |
>>>> You probably misunderstood. I didn't mean inactive in |
30 |
>>>> general, but inactive in a _project_. |
31 |
> |
32 |
> |
33 |
>>> Err no. That's not our job. If the project has an inactive |
34 |
>>> leader or member it's the leaders job (or team's job if the |
35 |
>>> leader is inactive) to sort this out internally. If that |
36 |
>>> fails, then they should seek help. undertakers do not have (and |
37 |
>>> neither want) the authority to remove active developers from |
38 |
>>> certain projects. If a project appears to be dead even though |
39 |
>>> it's members (and/or leader) are active in other Gentoo areas, |
40 |
>>> and they refuse to fix the situation, you may want to take this |
41 |
>>> to the Council. Seem like you need to re-read |
42 |
> |
43 |
>>> http://www.gentoo.org/proj/en/glep/glep-0039.html |
44 |
> |
45 |
> |
46 |
> |
47 |
>> I have read that and that is why I propose that undertakers do |
48 |
>> also check projects for their internal activity patterns. |
49 |
> |
50 |
>> I don't really think that is a job for the council. |
51 |
> |
52 |
> |
53 |
> Sorry it's not going to happen. |
54 |
|
55 |
ok. |
56 |
-----BEGIN PGP SIGNATURE----- |
57 |
Version: GnuPG v2.0.22 (GNU/Linux) |
58 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
59 |
|
60 |
iQEcBAEBAgAGBQJSXa7MAAoJEFpvPKfnPDWz9p8H/iBE3B5vQfqhWcd8vMwyG8oI |
61 |
5bjkQ/7Dq1CVPB/7h16oR6fiSauI5I2d+PNL/uSTacfA0j1SVsUEtWKjeMM5eL2u |
62 |
1doyB/o+z6Bww5LNYjnH/F8jHloJP/83bNmpDJZS/Mqb+0TrJ61EeimLcEBTBn7m |
63 |
1laT8ulxsIwypD/Blut7zcsvUQoazE9JlnLONO7i6eRMS0vEJLJTiHmSKLDB4Fv5 |
64 |
xoqvMJG5/6c1+EgKQzPxGUN0wo6Zw8aLTpSUkcYnacAAKzm+HGtBpvze2G1pv7eF |
65 |
Cu6XD4SHC9MMrKjdbxRyHso2f3N38sMC7SDnLKEOrrNus/M+OGtY25iv7zAQkmY= |
66 |
=gA6U |
67 |
-----END PGP SIGNATURE----- |