On Sun, 11 Jun 2006 07:33:19 -0400 Peter <[EMAIL PROTECTED]> wrote: > On Sat, 10 Jun 2006 13:37:15 +0200, Markus Ullmann wrote: > > > 1) m-w / m-n requirement > > > > Only ebuilds that are reported to bugzie (valid bug#) and set to > > maintainer-wanted are allowed here as well as maintainer-needed > > ones. > > > > maintainer-needed are only allowed if they're removed from the tree > > and moved over to sunrise (and thus end up as maintainer-wanted > > again). > > > > Um, there are numerous "new" not-in-portage-tree ebuilds submitted to > bz which have been assigned to teams. However, they may still > languish. They were assigned by the wranglers, and not improperly. > Yet, for many reasons, the bugs wait. So, will there be a mechanism > for a contributor to get an ebuild uploaded to sunrise in this > circumstance?
What those bugs are waiting for is a dev to step up and agree to maintain it. I don't see how sunrise improves that situation. The only way such a bug will be resolved if no dev is interested, is if someone who wants the package in the tree decides to become a dev - and that means demonstrating technical ability, and sticking around (not just dumping it in the tree then disappearing - in which case the package would likely get removed after a while anyway due to lack of maintenance). > I would also suggest having some sort of review process for inclusion > of m-n/m-w bugs. Some may not have any relevance (i.e. the program is > no longer supported, or the upstream project has been incorporated > into a new one, or the version of dated). Doing a blanket import of > m-w bugs could make quite a mess of things IMO. > > One of the terrific benefits of sunrise will be the cleaning out of > bugzilla. Nuking open bugs is an especially satisfying experience! Sorry, I don't buy that. Having m-w/m-n packages in the sunrise overlay cannot be sufficient to close the bugs in bugzilla. The bugs get closed when the package gets maintenance support from a dev and is put into the tree. Sunrise doesn't do anything to make that more likely. I also don't think that having large numbers of bugs open in bugzilla is a problem. The search facilities are quite capable of giving you focused lists of open bugs. If you don't want to see the bugs about m-w/m-n ebuilds, filter them out of your search. > Lastly, what about user contributions? Will users require some kind of > sponsorship in order to have their ebuilds posted? What will the > procedure be (or did I miss it in one of the hundreds of emails)? This reflects back on the primary objection to sunrise on gentoo.org. Your question is essentially, "who will take responsibility for it and put it in the tree?". Sunrise might help in getting ebuilds to a decent standard, and it might help some users to contribute, but it won't help if no dev wants to take on maintainership of the package. That last point is the only reason why m-w/m-n packages are not in the tree. -- Kevin F. Quinn
signature.asc
Description: PGP signature
