Mart Raudsepp wrote:
Hello,
I have had this project in my mind for a while, so it's about time to
get it out there, as to see if feedback finds it a good one - and if
that is so, if there are people who want to make it happen.
<snip>
Hmm, I wonder what the point is when there is 400 maintainer-needed bugs
open..
I think a maintainer-wanted team won't accomplish much because it just
uses more developer time from a pool of "not enough time" that exists
already. If people are a) too lazy to contribute to sunrise, b) don't
know about sunrise, or c) don't know enough about ebuilds to contribute
to sunrise, then we need to fix[1] that.
I don't see any reason to create a team that duplicates the sunrise
work. Keep in mind, I am against pretty much any overlay, I think work
should be kept in the main tree. But, for ebuild maintenance with
limited developer time, sunrise just makes sense(tm).
Some other possible directions include:
1) maintainer-needed team - Where a group maintains the set of 761
m-needed packages.
2) proxy maint project[2] - Where a group helps users commit to the main
tree, very similar to the sunrise project. Very similar to this proposal
but better conserves our developer time.
-Jeremy
[1]: http://dev.gentoo.org/~darkside/sunrise_proposal.txt
http://dev.gentoo.org/~darkside/sunrise_status.txt
[2]: http://dev.gentoo.org/~antarus/projects/proxy-maint/
