1 |
On 31-08-2010 10:03, Robin H. Johnson wrote: |
2 |
> On Mon, Aug 30, 2010 at 11:13:15PM +0200, Michael Weber wrote: |
3 |
>> Hello fellow developers. |
4 |
>> |
5 |
>> On 08/30/2010 04:20 PM, Dirkjan Ochtman wrote: |
6 |
>>> Sounds good to me, but I'd actually be more interested in having |
7 |
>>> something the other way around; i.e. monitoring for activity in |
8 |
>>> commits, bugzilla, IRC and maybe the -dev mailing list to see if |
9 |
>>> people are still active and send them a message to encourage them to |
10 |
>>> set devaway if they haven't been active in, say, 15 days. |
11 |
>> |
12 |
>> I think the intention was to force actually active developers to |
13 |
>> remove their out-of-date .away message, which isn't very representative |
14 |
>> for the project. |
15 |
> .away age statistics, as of right now (2010/08/31, 07:27 UTC). |
16 |
> - 53 developers with .away files. |
17 |
> - Oldest: 2007/Mar/01 (1278.8 days old). |
18 |
> - Mean: 153 days old. |
19 |
> - Median: 55.5 days. |
20 |
> - First, Third quartiles: 23.3, 136.5 days. |
21 |
> |
22 |
> What do the numbers mean? My opinion looking at them is that MOST |
23 |
> developers are using the .away system correctly, however some developers |
24 |
> just have forgotten to remove old .away files (they claimed they would |
25 |
> be back by a date, and commits started up after that). |
26 |
> |
27 |
> I'll fully admit that I neglected to remove my last .away until I |
28 |
> double-checked earlier today. |
29 |
|
30 |
Yes, it was my case also. I thought I removed it though, but it was just |
31 |
my memory playing tricks. |
32 |
|
33 |
Thanks for raising the thread :) |
34 |
> |
35 |
> How about this as an idea: |
36 |
> 1. Include a parsaable return date I suggest ("Returning:YYYY/MM/DD", |
37 |
> "Returning:Unknown") |
38 |
> 2. Automated emails when: |
39 |
> 2.1. It's after the return date (weekly). |
40 |
> 2.2. You start committing again. |
41 |
> |
42 |
|
43 |
Notifying about the away state when you commit, sounds great. |