On Sat, 10 Jun 2006 10:27:29 -0400
Chris Gianelloni <[EMAIL PROTECTED]> wrote:

[lots of good stuff - +lots Chris]

> Not so many moons ago, new ebuilds were submitted to bugzilla.  The
> bug wranglers would assign the bugs to the team most likely to end up
> as the maintainers, and new ebuilds either made it into the tree, or
> sat in bugzilla until the interest was there for it to be added, if
> ever.  Some people felt that this process left lots of packages in
> bugzilla, with no one to watch over them.  Because of this, the
> maintainer-wanted, and maintainer-needed bugzilla accounts were
> created to assist in tracking these bugs/packages.  This was a good
> idea at the time, and worked fairly well so long as there were
> developers going through and actively searching for bugs, that were
> no longer assigned to the relevant teams, but instead, assigned into
> some big dumping ground for new package requests.

I think it's clear that the maintainer-wanted/maintainer-needed hasn't
actually solved the problem it was trying to address. While it has
improved on some counts, I think the fact that herd maintainers
are not watching those aliases means that new builds are not being
brought to the attention of the devs most likely to take them on.

Instead of having sunrise on gentoo.org, which I agree with Chris is
fundamentally a bad idea, could we simply go back to assigning new
builds to the most relevant herd alias, but also add
maintainer-wanted/needed to the CC:?  That way some responsibility is
assigned to the herd to deal with it one way or another. If the
herd does not have the manpower to deal with it they can just reassign
to maintainer-needed and CC the herd, indicating they need someone
to join the group of herd maintainers to take the package on. With
maintainer-* on CC the benefits accrued so far from having a bunch of
people helping to iron out early QA problems would remain, and at the
same time the group of people most likely to pick up the package would
also be aware of it.

-- 
Kevin F. Quinn

Attachment: signature.asc
Description: PGP signature

Reply via email to