| 1 |
On Sat, 10 Jun 2006 13:37:15 +0200, Markus Ullmann wrote: |
| 2 |
|
| 3 |
> 1) m-w / m-n requirement |
| 4 |
> |
| 5 |
> Only ebuilds that are reported to bugzie (valid bug#) and set to |
| 6 |
> maintainer-wanted are allowed here as well as maintainer-needed ones. |
| 7 |
> |
| 8 |
> maintainer-needed are only allowed if they're removed from the tree and |
| 9 |
> moved over to sunrise (and thus end up as maintainer-wanted again). |
| 10 |
> |
| 11 |
|
| 12 |
Um, there are numerous "new" not-in-portage-tree ebuilds submitted to bz |
| 13 |
which have been assigned to teams. However, they may still languish. They |
| 14 |
were assigned by the wranglers, and not improperly. Yet, for many reasons, |
| 15 |
the bugs wait. So, will there be a mechanism for a contributor to get an |
| 16 |
ebuild uploaded to sunrise in this circumstance? |
| 17 |
|
| 18 |
I would also suggest having some sort of review process for inclusion of |
| 19 |
m-n/m-w bugs. Some may not have any relevance (i.e. the program is no |
| 20 |
longer supported, or the upstream project has been incorporated into a new |
| 21 |
one, or the version of dated). Doing a blanket import of m-w bugs could |
| 22 |
make quite a mess of things IMO. |
| 23 |
|
| 24 |
One of the terrific benefits of sunrise will be the cleaning out of |
| 25 |
bugzilla. Nuking open bugs is an especially satisfying experience! |
| 26 |
|
| 27 |
Lastly, what about user contributions? Will users require some kind of |
| 28 |
sponsorship in order to have their ebuilds posted? What will the procedure |
| 29 |
be (or did I miss it in one of the hundreds of emails)? |
| 30 |
|
| 31 |
-- |
| 32 |
Peter |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives