Hi, On Saturday 01 December 2007 12:35, Mario Iseli wrote: > One point was defining fixed intervals of pinging a maintainer and how we > could automate them, my proposal would be the following: > > X-MIA-Summary: nice Then wait 30 days > X-MIA-Summary: prod Then wait 30 days > X-MIA-Summary: last-warning Then wait 60 days > -> Orphan all packages and wait for 90 days again I also think this is unneccessary long. If someone doesnt respond for 120 days tomia queries, bugs are most probably also not answered within that period. I would suggest: X-MIA-Summary: nice Then wait 15 days X-MIA-Summary: just resend the nice mail in case it go lost Then wait 15 days X-MIA-Summary: prod Then wait 30 days X-MIA-Summary: last-warning Then wait 15 days -> Orphan all packages and wait for 90 days Which would reduce the time until packages get orphaned to 75 days. Even someone who is very busy in RL should be able to respond in that timeframe. And if not, well bugs doesnt get fixed then neither. Also, if a package has been orphaned, it takes a single mail to get it back. So IMO that's no big deal. > The initial contact and the last-warning should be written by hand and be > nice - the other mails can be templates. I agree with that, but suggest that the initial and last mail also contain a template part, where this procedure is described. No need to write this manually again and again :) > for the MIA-Team on Merkel. (By the way - "mia" is still no group, it's > just "qa" and it seems to be not so easy to become a member of this group, > so, what about adding a extre-group for MIA?) I dont think it's a good idea to add another layer of priviledges here. I think the solution is rather to make it easier to become member of the qa group (why is it hard?) - but maybe I'm missing something why it is useful (and no workaround) to have different groups for mia and qa. And if you really want a mia group, you should open a ticket at rt.debian.org :-) I havent checked if this has been done already. Disclaimer: I have no experience with MIA work. regards, Holger
Attachment:
pgpvf6HyMGNuN.pgp
Description: PGP signature