| 1 |
On Mon, Aug 30, 2010 at 07:36:29PM +0300, Petteri Räty wrote: |
| 2 |
> On 08/30/2010 05:14 PM, Markos Chandras wrote: |
| 3 |
> > Hi there |
| 4 |
> > |
| 5 |
> > It seems to me that people paying less and less attention to devaway |
| 6 |
> > system[1]. As you may see yourselves, few of the entries are 2-3 year old. This |
| 7 |
> > either means that these devs are inactive since then or that they came back |
| 8 |
> > and just didn't bother updating their status. Is it possible for infra people |
| 9 |
> > to setup a script to notify the developer ( and CC the retirement alias ) |
| 10 |
> > about an old devaway entry? |
| 11 |
> |
| 12 |
> I can't speak for infra but seems like it would be useful. Anyone could |
| 13 |
> write a script that infra could put under cron. |
| 14 |
|
| 15 |
find /home/ -name ".away" -mtime +60 -exec sendmail -t <developer> <message.txt> placed on dev box should be a good starting point. |
| 16 |
|
| 17 |
where message.txt could be |
| 18 |
|
| 19 |
" From: devaway-alert@g.o |
| 20 |
To: <developer> |
| 21 |
CC: retirement@g.o |
| 22 |
Subject: Your devaway message is too old |
| 23 |
[....] |
| 24 |
" |
| 25 |
|
| 26 |
> |
| 27 |
> > This will help retirement team to track down |
| 28 |
> > inactive devs with ease. |
| 29 |
> |
| 30 |
> Retirement team already has scripts that do good enough job on finding |
| 31 |
> not active people. Jorge can comment on (if he happens to read this) if |
| 32 |
> they have enough man power at hand currently to act on the output. |
| 33 |
> |
| 34 |
Yeah I do know that but my biggest concern is the status update of this page |
| 35 |
rather than using it for spotting inactive devs |
| 36 |
> > Furthermore having so many devs with away messages ( |
| 37 |
> > where only part of the messages reflect the reality ) looks quite bad to |
| 38 |
> > community. I think that a simple script that will search all the devaway |
| 39 |
> > messages and collect those that are >60-90 days is not that difficult to get |
| 40 |
> > implemented. Does anybody have a better approach to deal with this? |
| 41 |
> > |
| 42 |
> |
| 43 |
> I think this message should have been sent to gentoo-project. |
| 44 |
Yeah that's true :-/ We can move the discussion there if you want |
| 45 |
> |
| 46 |
> Regards, |
| 47 |
> Petteri |
| 48 |
> |
| 49 |
|
| 50 |
-- |
| 51 |
Markos Chandras (hwoarang) |
| 52 |
Gentoo Linux Developer |
| 53 |
Web: http://hwoarang.silverarrow.org |
| 54 |
Key ID: 441AC410 |
| 55 |
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410 |
Archives