| 1 |
"Wulf C. Krueger" <philantrop@g.o> posted |
| 2 |
200706071650.54612.philantrop@g.o, excerpted below, on Thu, 07 Jun |
| 3 |
2007 16:50:54 +0200: |
| 4 |
|
| 5 |
> I mostly agree with your arguments but seeing what we have in the |
| 6 |
> Sunrise overlay I don't think we need another one. |
| 7 |
> |
| 8 |
> Today, people can get involved by submitting ebuilds to (and maintaining |
| 9 |
> them in) Sunrise rather easily. As easily as devs can take ebuilds from |
| 10 |
> there and add them to the official tree. |
| 11 |
> |
| 12 |
> What would/should be different compared to that if we implemented your |
| 13 |
> suggestion? |
| 14 |
|
| 15 |
The difference, as I read the proposal, is that while Sunrise is about |
| 16 |
packages that are /not/ in the main tree yet (if it's moved to the tree, |
| 17 |
it's out of sunrise, tho it might move to another overlay if |
| 18 |
appropriate), this proposal would extend that to packages that are in the |
| 19 |
tree as well. |
| 20 |
|
| 21 |
(Vetted) users could commit to in-tree packages, but only in the (main) |
| 22 |
development overlay. It'd be Sunrise, but just as devs watch what's |
| 23 |
going on there with the eventual goal of getting some of the ebuilds into |
| 24 |
the tree, so here, devs would watch and make commits to the (mirrored) |
| 25 |
tree from the development overlay. |
| 26 |
|
| 27 |
I've not read the rest of the responses yet, but the question I had |
| 28 |
was... OK, but won't that result in either (a) developers getting /more/ |
| 29 |
bump/test/grind, not less, since more of it would be taking commits |
| 30 |
already made by users and applying them to the mirrored tree (the |
| 31 |
committing users get more of the creativity, the devs end up being just |
| 32 |
shuttle monkeys, vetting then shuttling from the dev tree to the mirrored |
| 33 |
tree), or (b) the mirrored tree eventually falling seriously behind? IMO |
| 34 |
there may need to be mechanisms to prevent it from going one way or the |
| 35 |
other, as I don't otherwise see the proposed situation of dev then |
| 36 |
mirrored tree as being stable over time -- it'll lean toward a or b above. |
| 37 |
|
| 38 |
-- |
| 39 |
Duncan - List replies preferred. No HTML msgs. |
| 40 |
"Every nonfree program has a lord, a master -- |
| 41 |
and if you use the program, he is your master." Richard Stallman |
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-dev@g.o mailing list |
Archives