Currently, things assigned to maintainer-wanted get the following keywords (bugzilla, not ebuild):
* EBUILD if an ebuild is attached * REQUEST if an ebuild is requested I've been going through the EBUILD list at random and providing lists of things that need to be fixed before the ebuild can be considered for inclusion. The WONTFIX resolution along with a comment asking for the submitter to reopen with a fixed ebuild is used when problems are found. Note that I'm being pretty strict about quoting, style etc, partly because one easy way of improving tree QA is by making sure that new entries are of a high standard and partly because it would be nice for herds to be able to get a perfect, probably no changes needed ebuild. Sure, some of the existing tree is far from ideal, but that's no excuse for adding new shoddy things. What I'd like is a new keyword (bugzilla, not ebuild) for indicating that a developer has done a check on an ebuild and is satisfied that the ebuild is fine from a style perspective. This does **not** mean that the developer has tried to actually merge the package. There're all kinds of things for which I can say "the ebuild looks good", but not so many for which I can say "the ebuild looks good and installs something that works", since a lot of them have insanely long dependency lists or specific hardware requirements. Can anyone suggest a name? Best I can come up with is STYLE_CHECKED(nickname)... Hopefully it will reduce herd loads significantly if it can be ensured that they're only sent high quality ebuilds... -- Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
pgpenq51Z5Dbu.pgp
Description: PGP signature
