On Mon, Aug 30, 2010 at 07:36:29PM +0300, Petteri Räty wrote:
> On 08/30/2010 05:14 PM, Markos Chandras wrote:
> > Hi there
> > 
> > It seems to me that people paying less and less attention to devaway
> > system[1]. As you may see yourselves, few of the entries are 2-3 year old. 
> > This
> > either means that these devs are inactive since then or that they came back
> > and just didn't bother updating their status. Is it possible for infra 
> > people
> > to setup a script to notify the developer ( and CC the retirement alias )
> > about an old devaway entry? 
> 
> I can't speak for infra but seems like it would be useful. Anyone could
> write a script that infra could put under cron.

find /home/ -name ".away" -mtime +60 -exec sendmail -t <developer> 
<message.txt> placed on dev box should be a good starting point.

where message.txt could be

" From: [email protected]
  To: <developer>
  CC: [email protected]
  Subject: Your devaway message is too old
  [....]
 "

> 
> > This will help retirement team to track down
> > inactive devs with ease.
> 
> Retirement team already has scripts that do good enough job on finding
> not active people. Jorge can comment on (if he happens to read this) if
> they have enough man power at hand currently to act on the output.
> 
Yeah I do know that but my biggest concern is the status update of this page
rather than using it for spotting inactive devs
> > Furthermore having so many devs with away messages (
> > where only part of the messages reflect the reality ) looks quite bad to
> > community. I think that a simple script that will search all the devaway
> > messages and collect those that are >60-90 days is not that difficult to get
> > implemented. Does anybody have a better approach to deal with this?
> > 
> 
> I think this message should have been sent to gentoo-project.
Yeah that's true :-/ We can move the discussion there if you want
> 
> Regards,
> Petteri
> 

-- 
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410

Attachment: pgpPM4ZBMzHJV.pgp
Description: PGP signature

Reply via email to