1 |
On Sun, Jun 11, 2006 at 06:53:51PM +0100, Stuart Herbert wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> Henrik Brix Andersen wrote: |
6 |
> | However, as has been pointed out several times in this thread already, |
7 |
> | back when the devloper community agreed to the overlays project it was |
8 |
> | also agreed that projects similar to what is now known as Project |
9 |
> | Sunrise was not be present on overlays.gentoo.org. |
10 |
> |
11 |
> Can you provide a reference to this, please? I've been through my -dev M/L |
12 |
> archive several times, and cannot find an email where I agreed to this. |
13 |
|
14 |
Perhaps not in those exact words, I admit. But the general consensus |
15 |
in my eyes, and I'm not alone with this view according to other |
16 |
replies to this thread, was that the purpose of overlays.gentoo.org |
17 |
would be to provide a common place to host project and developer |
18 |
overlays - not a place to host Joe User's ebuild contributions (except |
19 |
for users regularly contributing to specific teams/herds and |
20 |
devs-in-spee). [1] [2] [3] |
21 |
|
22 |
You could argue that Project Sunrise *is* a specific project. Fact is |
23 |
that nobody at that time could predict that a small group of |
24 |
developers would go ahead and create a project with the single goal of |
25 |
providing Joe User's bugzilla-contributed ebuilds to end-users through |
26 |
overlays.gentoo.org. |
27 |
|
28 |
In my opinion, creating a new project with this purpose should not |
29 |
have been allowed. I fear that perhaps creating the project was just |
30 |
an attempt to circumvent the policy of overlays.gentoo.org, which |
31 |
states that only project teams and individual Gentoo developers can |
32 |
have an overlay on overlays.gentoo.org. It seems that the developers |
33 |
who started Project Sunrise already planed to use overlays.gentoo.org |
34 |
as a "free-for-all" overlay with no QA and policy checks back when the |
35 |
idea of an official overlays project was discussed. [4] [5] |
36 |
|
37 |
The security issues of having an official overlay of unsupported |
38 |
ebuilds was also raised back then. [6] [7] [8] [9] [10] As was the |
39 |
concerns about potential damage to the reputation of Gentoo as a |
40 |
whole. [11] [12] |
41 |
|
42 |
On the other hand, having team/herd specific overlays with commit |
43 |
access from a select few end-users (as was written in the original |
44 |
proposal) was seen as a good idea. [13] [14] |
45 |
|
46 |
I've spent tonight reading through the entire thread that let to the |
47 |
creation of the overlays project, and I still come out in the end with |
48 |
the feeling that a consensus of having overlays.gentoo.org for hosting |
49 |
the already existing developer and herd/team overlays in a central |
50 |
place was reached. It also looks to me like the idea of having a |
51 |
"free-for-all" or a user-contrib overlay hosted there would not be |
52 |
acceptable due to security issues and risk of damaging the reputation |
53 |
of Gentoo as a whole. |
54 |
|
55 |
I know this doesn't provide solid evidence that this is how it was, |
56 |
but truth is - we hardly ever see an email on the developers list |
57 |
stating "This is what we agreed on". Due to the nature of the media we |
58 |
tend to have a lot of input and discussion back and forth after which |
59 |
a general consensus is found. This consensus, as I see it, is |
60 |
reflected in the policy for overlays.gentoo.org. [15] |
61 |
|
62 |
I urge people to read through the initial thread that fostered |
63 |
overlays.gentoo.org as well - if only to refresh peoples memory on the |
64 |
stuff that was discussed back then. You can start at |
65 |
http://www.mail-archive.com/gentoo-dev@l.g.o/msg09877.html |
66 |
|
67 |
Sincerely, |
68 |
Brix |
69 |
|
70 |
[1]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09913.html |
71 |
[2]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09921.html |
72 |
[3]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09983.html |
73 |
|
74 |
[4]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09962.html |
75 |
[5]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09966.html |
76 |
|
77 |
[6]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09918.html |
78 |
[7]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09959.html |
79 |
[8]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09884.html |
80 |
[9]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09964.html |
81 |
[10]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09963.html |
82 |
[11]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09910.html |
83 |
[12]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09946.html |
84 |
|
85 |
[13]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09948.html |
86 |
[14]: http://www.mail-archive.com/gentoo-dev@l.g.o/msg09972.html |
87 |
|
88 |
[15]: http://www.gentoo.org/proj/en/overlays/policy.xml |
89 |
-- |
90 |
Henrik Brix Andersen <brix@g.o> |
91 |
Gentoo Metadistribution | Mobile computing herd |