1 |
On 08/30/10 08:20, Dirkjan Ochtman wrote: |
2 |
> On Mon, Aug 30, 2010 at 16:14, Markos Chandras <hwoarang@g.o> wrote: |
3 |
>> It seems to me that people paying less and less attention to devaway |
4 |
>> system[1]. As you may see yourselves, few of the entries are 2-3 year old. This |
5 |
>> either means that these devs are inactive since then or that they came back |
6 |
>> and just didn't bother updating their status. Is it possible for infra people |
7 |
>> to setup a script to notify the developer ( and CC the retirement alias ) |
8 |
>> about an old devaway entry? This will help retirement team to track down |
9 |
>> inactive devs with ease. Furthermore having so many devs with away messages ( |
10 |
>> where only part of the messages reflect the reality ) looks quite bad to |
11 |
>> community. I think that a simple script that will search all the devaway |
12 |
>> messages and collect those that are >60-90 days is not that difficult to get |
13 |
>> implemented. Does anybody have a better approach to deal with this? |
14 |
>> |
15 |
>> Thanks |
16 |
>> |
17 |
>> [1]: http://www.gentoo.org/proj/en/devrel/roll-call/devaway.xml |
18 |
> |
19 |
> Sounds good to me, but I'd actually be more interested in having |
20 |
> something the other way around; i.e. monitoring for activity in |
21 |
> commits, bugzilla, IRC and maybe the -dev mailing list to see if |
22 |
> people are still active and send them a message to encourage them to |
23 |
> set devaway if they haven't been active in, say, 15 days. |
24 |
|
25 |
Please no. |