1 |
Mart Raudsepp schrieb: |
2 |
>> If people are a) too lazy to contribute to sunrise, b) don't |
3 |
>> know about sunrise, or c) don't know enough about ebuilds to contribute |
4 |
>> to sunrise, then we need to fix[1] that. |
5 |
> |
6 |
> Sure, the sunrise project can do all of that. That doesn't make the |
7 |
> packages available in the official tree. The maintainer-wanted project |
8 |
> however can tap into the work done by sunrise when a popular package is |
9 |
> to be added to the tree that already exists in Sunrise. If certain |
10 |
> interested in the package users are contributing to Sunrise for that |
11 |
> package, they could hopefully be turned into proxy maintainers in the |
12 |
> official tree version and perhaps even eventually become developers as |
13 |
> well when they have interest in a larger set of packages. If they have |
14 |
> been maintaining a lot of different package in Sunrise before that, they |
15 |
> seem to be a good candidate in joining the maintainer-wanted team too |
16 |
> then, as they seem to be motivated by the kind of work they do, as same |
17 |
> work was done in an overlay by him/her before. |
18 |
> Close collaboration with Sunrise is good, that is. So the end outcome |
19 |
> would be that the packages that are used by many people are available in |
20 |
> the official tree. |
21 |
|
22 |
I think, you overrate the possible additional free time that developers are able and willing to |
23 |
contribute to Gentoo for such a project. |
24 |
If a dev is intersted in a package, he can create an ebuild, add it to the main tree and maintain it |
25 |
there. |
26 |
If a dev would like to add a popular package, also not being personally interested, he can still do |
27 |
it, nothing prevents him from that. |
28 |
But this does not happen and i think, there is a simple reason: The number of active developers with |
29 |
access to the main tree is limited and the amount of work they can do is it too. In the end, this |
30 |
project would create some or even many packages, that end as m-needed because the team is not |
31 |
willing or able to maintain the amount of ebuilds they initially added. |
32 |
If users are interested in a package and willing to create an ebuild and maintain it, they can add |
33 |
it to the sunrise overlay. If they do continual good work, they can even become developers |
34 |
themselves and move some apps to the main tree (like i did). If they dont continue the maintainence, |
35 |
the ebuild will stay in sunrise as a base for everyone interested without polluting the main tree. |
36 |
|
37 |
Based on this, i would suggest another basic idea (details can be discussed, if accepted): |
38 |
|
39 |
-Make the sunrise overlay more known on different places like front page, blogs, forum etc |
40 |
|
41 |
-Based on some checks (good QA, maintained, fixed reported problems or whatever), add good ebuilds |
42 |
to the main tree with some restrictions (maybe some additional var, only unstable keywords or |
43 |
similar). If there are no complains and bugs get fixed (either some dev or the maintainer (user) |
44 |
does it), it will stay there, if not, it gets removed from the tree again and moved back to the |
45 |
sunrise overlay. |
46 |
|
47 |
Whith this, users would get a central place to start with reading, contributing, learning and proxy |
48 |
maintaining their ebuilds, would be able to get their work to some audience (either those adding |
49 |
sunrise overlay or with good work even the main tree), could learn enough to become developers with |
50 |
main tree access themselves. And if they leave their work alone, it just gets moved from the main |
51 |
tree back to the sunrise overlay and so cannot harm Gentoo, the security team or anyone else for a |
52 |
longer time. |
53 |
|
54 |
Just for clarification: Those contributors would still only commit to a branch not accessable via |
55 |
layman nor does it automaticly write to the main tree. These contributions then get currently moved |
56 |
to the reviewed tree (which is what users get via layman) after some sunrise dev did review the |
57 |
commit. In this proposal, the move to the main tree and any update would go the same way, so no |
58 |
direct access to the main tree by (user) contributors until they got recruited as ebuild deveopers. |
59 |
|
60 |
With this proposal, we could recruite new people to work on things they are intersted in, so it |
61 |
should be relatively easy to get popular packages in the main tree, while not using some (probably |
62 |
not existing) additional dev-time. |
63 |
|
64 |
|
65 |
-- |
66 |
Thomas Sachau |
67 |
|
68 |
Gentoo Linux Developer |