On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos <pa...@gentoo.org> wrote: > > Personally I would vote for simply have a <maintainer> tag pointing to > the alias but we would still need to keep a list of real maintainers for > that alias as usually not all people listed in the alias are willing to > maintain the packages. >
I think the solution to this is that maintainers can be either: 1. Devs - identified by their email address. (simple enough) or 2. Projects - identified by their email alias. or 3. A proxy maintainer identified by email address (in which case either a dev or project must also be listed, potentially including the proxy maintainer project). A project must have: 1. A mail alias. Anybody can monitor if the project is OK with it, but it isn't the definitive member list. 2. A project page on the wiki with a member list. This is the definitive list of who is a member. 3. An annually-elected lead. The lead should clean up the member list from time to time. An inactive project should be treated the same as an inactive dev as far as maintainership goes - target for cleanup. Special projects like archs/infra/comrel/etc should probably be escalated to council if they appear dead. Herds are just collections of packages - a package being in a herd says nothing about whether it is maintained, just as a package being in a category says nothing about it being maintained. -- Rich
