1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA512 |
3 |
|
4 |
On 10/15/2013 09:53 PM, hasufell wrote: |
5 |
> On 10/15/2013 10:46 PM, Markos Chandras wrote: |
6 |
>> On 10/15/2013 09:40 PM, hasufell wrote: |
7 |
>>> On 10/15/2013 10:28 PM, Markos Chandras wrote: |
8 |
>>>> On 10/15/2013 09:16 PM, hasufell wrote: |
9 |
>>>>> I wonder if undertakers should also check for inactive |
10 |
>>>>> project leaders/members and remove them from the projects |
11 |
>>>>> in case there has not been any activity for a while, |
12 |
>>>>> regardless of the internal project structure. |
13 |
>>>> |
14 |
>>>>> Authority does not only come with knowledge, but also with |
15 |
>>>>> commitment. |
16 |
>>>> |
17 |
>>>>> If no one disagrees, then we should add this to the list of |
18 |
>>>>> undertakers competence. |
19 |
>>>> |
20 |
>>>> |
21 |
>>>> We already check for inactive members (developers and |
22 |
>>>> leaders are the same for us) |
23 |
>>>> |
24 |
>>>> What's is this thread for? |
25 |
>>>> |
26 |
>>>> |
27 |
> |
28 |
>>> You probably misunderstood. I didn't mean inactive in general, |
29 |
>>> but inactive in a _project_. |
30 |
> |
31 |
> |
32 |
>> Err no. That's not our job. If the project has an inactive |
33 |
>> leader or member it's the leaders job (or team's job if the |
34 |
>> leader is inactive) to sort this out internally. If that fails, |
35 |
>> then they should seek help. undertakers do not have (and neither |
36 |
>> want) the authority to remove active developers from certain |
37 |
>> projects. If a project appears to be dead even though it's |
38 |
>> members (and/or leader) are active in other Gentoo areas, and |
39 |
>> they refuse to fix the situation, you may want to take this to |
40 |
>> the Council. Seem like you need to re-read |
41 |
> |
42 |
>> http://www.gentoo.org/proj/en/glep/glep-0039.html |
43 |
> |
44 |
> |
45 |
> |
46 |
> I have read that and that is why I propose that undertakers do |
47 |
> also check projects for their internal activity patterns. |
48 |
> |
49 |
> I don't really think that is a job for the council. |
50 |
> |
51 |
|
52 |
Sorry it's not going to happen. We can't just go ahead asking all the |
53 |
projects for a list of active/inactive people every couple of months |
54 |
or so. This does not scale, and we do not want to become annoying to |
55 |
other developers. Like I said, if a project is completely dead someone |
56 |
will notice. If you have found such a project, and you talked to them, |
57 |
and they refuce to fix it, then taking this to the Council is the |
58 |
right way to solve this problem. |
59 |
If the project has a few inactive people then the team or the lead can |
60 |
sort this out themselves. |
61 |
|
62 |
- -- |
63 |
Regards, |
64 |
Markos Chandras - Gentoo Linux Developer |
65 |
http://dev.gentoo.org/~hwoarang |
66 |
-----BEGIN PGP SIGNATURE----- |
67 |
Version: GnuPG v2.0.22 (GNU/Linux) |
68 |
|
69 |
iQJ8BAEBCgBmBQJSXa0HXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w |
70 |
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzNTVDNDczOUYzRjJEMTRGNDRGMzU2RkMw |
71 |
OUJGNEY1NEMyQkE3RjNDAAoJEAm/T1TCun88cFkQAMaU6/+PUhp8M7qFhCAiq2qG |
72 |
FEm+hwqZO27YAFdRH7vuTJRUYSFr6Iq5WRw+A2qXOuRt6jGahGWTBr23u+40/Jeq |
73 |
MqgUVFaTY7EFfPWea6KXicqJgZEWUMCx31H2T6Y6bgq0M8jsRjDwTIMo5JkVBFX0 |
74 |
I8LKJslYadRAW+BWci7W/AYBaVC45kebAdktv8a1diwzvC+5S5vl8/Rcw4mWXLFA |
75 |
jmQlXZOVk/hlyLVSU2x7xo9IcNradkEMRIWh87IQzr6UGO6sWoR1wtA2Kux/lWIw |
76 |
nOjyDk9ARaYq2WDxaR899Lt9yvUCJ04gi3SqMpimaOEYoaMc26RHM7q3awxtR6LW |
77 |
YcDmphFKNRAxES7j6e0tPt78wKff/FDckAz8Q2W0mSJ7Y+erJ2T6Eb4KBKjiGa7Q |
78 |
9iA8vJy5PfaF6/VINwEN3CWZQDS2I5pu5Bwwo/PS7SSR/dlYYKiriDYxEGt9fJeM |
79 |
YlXr+jF50Gd64b4zGoY16bw5XKgnops7uo+pu/1EcO3DYyvtujZmpSVNIb5n/H82 |
80 |
0kuXn2kkL5U4Gq2WouVGrV8Rjh9fGE3vUzdVvyCHdMFtdjB/RLu0exz520rmGK/+ |
81 |
4p6WgR7MQYDoIlTWPRpluZ2WAVfnY/zEg7tE8YeVqBpN2NY5uWd50SEUVY6rZjIW |
82 |
hZTyWWyKqElh1I6Y8vZD |
83 |
=ueym |
84 |
-----END PGP SIGNATURE----- |