Ned Ludd wrote: > from an infra POV vs a council POV I would say here is what we can do > right away to solve this. Arch testers will get added to an alias that > fordwards to the users normal email address. The aliases will be > maintained by the arch testing leads. The arch testers will have access > via the anoncvs repo when that is setup. If the arch testing lead fails > to keep his/her aliases up2date (excessive bounces, stale AT's etc..) > than they lose g+w rights to maintain the alias.
Actually, if this gets to the point where those leads have 100+ ATs to watch out for, I'd rather put the load of 'renewing' their alias on the AT themselves. The basic idea is, make them 'renew' their alias every 6 months via some php app (or whatever we come up with). A reminder could be sent out a month in advance. If they fail to update their renewal, their alias will expire and the lead will get a notification of that expiration. To me, if the ATs want to stick around, they should put forth the effort of keeping their info up to date. I know that devrel is having a hard enough time keeping up with developer staleness, and to me this is the 'simplest' solution to that problem. If they can't keep up with doing a simple renewal every 6 mo, then they don't have enough time to be an AT in my mind. -- Lance Albertson <[EMAIL PROTECTED]> Gentoo Infrastructure | Operations Manager --- GPG Public Key: <http://www.ramereth.net/lance.asc> Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net
signature.asc
Description: OpenPGP digital signature
