1 |
On Sun, 2006-06-11 at 07:33 -0400, Peter wrote: |
2 |
> On Sat, 10 Jun 2006 13:37:15 +0200, Markus Ullmann wrote: |
3 |
> |
4 |
> > 1) m-w / m-n requirement |
5 |
> > |
6 |
> > Only ebuilds that are reported to bugzie (valid bug#) and set to |
7 |
> > maintainer-wanted are allowed here as well as maintainer-needed ones. |
8 |
> > |
9 |
> > maintainer-needed are only allowed if they're removed from the tree and |
10 |
> > moved over to sunrise (and thus end up as maintainer-wanted again). |
11 |
> > |
12 |
> |
13 |
> Um, there are numerous "new" not-in-portage-tree ebuilds submitted to bz |
14 |
> which have been assigned to teams. However, they may still languish. They |
15 |
> were assigned by the wranglers, and not improperly. Yet, for many reasons, |
16 |
> the bugs wait. So, will there be a mechanism for a contributor to get an |
17 |
> ebuild uploaded to sunrise in this circumstance? |
18 |
|
19 |
No. If the ebuild belongs to a particular herd due to its function, |
20 |
then the decision/responsibility should fully stay with the herd. |
21 |
|
22 |
> One of the terrific benefits of sunrise will be the cleaning out of |
23 |
> bugzilla. Nuking open bugs is an especially satisfying experience! |
24 |
|
25 |
This project will not resolve a single bug. The bugs will remain open |
26 |
until they are included in the main tree. As I have stated before, this |
27 |
really solves nothing, it just migrates the "problem" to somewhere else |
28 |
and causes a much larger support problem for developers. |
29 |
|
30 |
> Lastly, what about user contributions? Will users require some kind of |
31 |
> sponsorship in order to have their ebuilds posted? What will the procedure |
32 |
> be (or did I miss it in one of the hundreds of emails)? |
33 |
|
34 |
You missed it, though it really wasn't apparent anywhere. The project |
35 |
will simple pick ebuilds that are "good enough" to go into the overlay. |
36 |
They have made no mention of how this will occur, until the recent |
37 |
posting of the "new" rules, which set the herd as the authority on what |
38 |
goes into the overlay. |
39 |
|
40 |
-- |
41 |
Chris Gianelloni |
42 |
Release Engineering - Strategic Lead |
43 |
x86 Architecture Team |
44 |
Games - Developer |
45 |
Gentoo Linux |