On Thursday 15 June 2006 10:57, Jakub Moc wrote: > > On Thursday 15 June 2006 02:33, Kevin F. Quinn wrote: > >> We could require that a herd mail alias be maintained for every herd, > >> with the same name as the herd, such that the herd alias lists the > >> maintainers of all packages in the herd. > > Two notes here: > > - same name as herd requirement doesn't work for stuff like > cron/mysql/postgresql/apache... i.e., system accounts. > > - needs to be done tree-wide (for packages that have metadata.xml at > least :P - ebuilds w/o metadata is topic for another thread). Until it's > completed, it's not useful - you still cannot rely upon the assumption > that if herd alias ain't in <maintainer>, they don't maintain the thing. > I don't know if this is a really unpopular viewpoint, but for a lot of stuff I maintain I put myself as maintainer and the herd I am acting as part of in herd. My intention there is to say primarily I am taking care of this and have taken responsibility but if I disappear, am slow or someone else just wants to bump it etc in that herd then they are also free to do so.
May be it would be more correct for me to add the herd alias as a second maintainer? I think it is good for people to take responsibility for what they add to the tree and that is my intention there...
pgptGKmOtlUZm.pgp
Description: PGP signature
