| 1 |
On Monday, August 30, 2010 10:14:48 Markos Chandras wrote: |
| 2 |
> It seems to me that people paying less and less attention to devaway |
| 3 |
> system[1]. As you may see yourselves, few of the entries are 2-3 year old. |
| 4 |
> This either means that these devs are inactive since then or that they |
| 5 |
> came back and just didn't bother updating their status. Is it possible for |
| 6 |
> infra people to setup a script to notify the developer ( and CC the |
| 7 |
> retirement alias ) about an old devaway entry? This will help retirement |
| 8 |
> team to track down inactive devs with ease. Furthermore having so many |
| 9 |
> devs with away messages ( where only part of the messages reflect the |
| 10 |
> reality ) looks quite bad to community. I think that a simple script that |
| 11 |
> will search all the devaway messages and collect those that are >60-90 |
| 12 |
> days is not that difficult to get implemented. Does anybody have a better |
| 13 |
> approach to deal with this? |
| 14 |
|
| 15 |
i'd extend the spec a little so that the dev can declare their expected return |
| 16 |
time and have the script ignore entries before that date |
| 17 |
|
| 18 |
perhaps say "the very last line should be just the date in YYYY-MM-DD format" |
| 19 |
-mike |
Archives