1 |
Asking developers to "proxy" takes almost as much time as it does to |
2 |
ask them to maintain a package by themselves. The developer is |
3 |
directly responsible for anything he commits, so he will have to still |
4 |
test the ebuild, still test any revisions, and still follow the |
5 |
package to make sure there are no problems. The writing the ebuild |
6 |
part of the process is not that much of the commitment, I don't see |
7 |
the point. |
8 |
|
9 |
On 3/22/06, Thomas Cort <linuxgeek@×××××.com> wrote: |
10 |
> > > A developer could then take these ebuilds, make sure they |
11 |
> > > don't do anything malicious, or break QA, or whatever, and act as the |
12 |
> > > bridge between the portage tree and the users actually working on the |
13 |
> > > ebuild and keeping things up to date and working. |
14 |
> |
15 |
> > The easiest way to handle "contrib" as far as that "big warning" is to |
16 |
> > make it a separate tree. That way, folks who want the flexibility get |
17 |
> > it, but those who prefer not to "risk it", don't have to worry about it. |
18 |
> > As well, contribs becomes another fertile developer recruitment ground. |
19 |
> |
20 |
> Why would the packages need a "big warning"/overlay/eclass if they |
21 |
> were checked by a developer to make sure they "don't do anything |
22 |
> malicious, or break QA, or whatever"? There are many user contributed |
23 |
> ebuilds that have made their way into portage after being reviewed by |
24 |
> devs that don't have any such warnings. |
25 |
> |
26 |
> I don't think creating a "contrib" overlay as an official part of |
27 |
> Gentoo would be a good idea because making it an official Gentoo |
28 |
> project conveys a certain level of quality. If the quality is there, |
29 |
> then why not add the ebuilds to portage in the first place? If the |
30 |
> quality isn't there, then you will have a lot of unhappy users |
31 |
> complaining that an official Gentoo overlay broke their system. |
32 |
> |
33 |
> Having a non-Gentoo sponsored contrib overlay wouldn't be a good idea |
34 |
> either IMO because the contributors wouldn't be contributing to |
35 |
> Gentoo, and they wouldn't be interacting as much with the Gentoo |
36 |
> developer community. Sure they would learn a lot of the skills |
37 |
> required to be a Gentoo developer, but they wouldn't be increasing the |
38 |
> value of anything in portage (unless they got a proxy to commit some |
39 |
> of their work to portage). Also, there are many overlays out there |
40 |
> already. Adding another one won't help with "making the developer |
41 |
> community more open". Additionally, I don't personally know of a lot |
42 |
> of people who actually use third party overlays except to get an |
43 |
> ebuild for a particular package they want or to beta test ebuilds. |
44 |
> |
45 |
> -Thomas |
46 |
> |
47 |
> -- |
48 |
> gentoo-dev@g.o mailing list |
49 |
> |
50 |
> |
51 |
|
52 |
-- |
53 |
gentoo-dev@g.o mailing list |