On Wednesday 22 March 2006 18:22, Christian Perrier wrote: > Agreed to both proposals. After all, I already did the last NMU of > fontforge, IIRC...:-) > > So, in about one week, if noone steps in, then we take the package > over. I propose setting the list as maintainer (either the list > itself..which means it would receive bug reports....or a dedicated > list for bugs, with an open posting policy, which is mandatory for bug > reports) Hmm. I'm absolutely not thrilled of seeing lists as maintainers of more and more packages. Ask our release managers - there were cases where a list was set as maintainer, and when the release mgr contacted the maintainer address because some relatively urgent action was necessary, nobody on that list felt compelled to react. Group maintenance yes, as in 'everybody of a group of people has commit permissions on that pkg' (and is allowed to add himself as Uploader instead of doing NMUs), but I feel it would be better for Debian if the maintainer were a real person, namely the person 'where the bucket stops', to avoid bug ping-pong in all variations. cheers -- vbi -- Cheap things are of no value, valuable things are not cheap.
Description: PGP signature