Peter wrote: > 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?
You need to ask a team member then to move them to maintainer-wanted. Usually the teams have no problem with moving bugs over to maintainer-wanted because they know that they cannot maintain everything themselves. > 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. This is volunteers work and usually volunteers are only moving over the ebuilds they use themselves. We are not doing this in a general way, but on a per-user per-package basis. We do not plan to run any importing scripts. It will only be done if a user or developer is interested in it :) > One of the terrific benefits of sunrise will be the cleaning out of > bugzilla. Nuking open bugs is an especially satisfying experience! Sorry, we are not doing this. We are assigning a bug to every sunrise ebuild to make sure that it can be discussed there and is still easily searchable. > > 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)? see 5) from Markus' email. You just need to have a good ebuild contribution that we can review with you, You will not gain full access but it is a start. - Stefan -- gentoo-dev@gentoo.org mailing list
