On Sun, 2006-06-11 at 07:33 -0400, Peter 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?
No. If the ebuild belongs to a particular herd due to its function, then the decision/responsibility should fully stay with the herd. > One of the terrific benefits of sunrise will be the cleaning out of > bugzilla. Nuking open bugs is an especially satisfying experience! This project will not resolve a single bug. The bugs will remain open until they are included in the main tree. As I have stated before, this really solves nothing, it just migrates the "problem" to somewhere else and causes a much larger support problem for developers. > 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)? You missed it, though it really wasn't apparent anywhere. The project will simple pick ebuilds that are "good enough" to go into the overlay. They have made no mention of how this will occur, until the recent posting of the "new" rules, which set the herd as the authority on what goes into the overlay. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
