1 |
Rich Freeman wrote: |
2 |
> >> This is not a great way to invite more users to participate. If you |
3 |
> >> intend to make the game overlay and team a developer-only thing you |
4 |
> >> are doing a great work. |
5 |
> > |
6 |
> > Everything in the Gentoo project is per definition strictly |
7 |
> > developer-only. I suppose that it's a function of having the |
8 |
> > project centered around a foundation. |
9 |
> |
10 |
> I can't think of any reason that the Foundation would have anything to |
11 |
> do with who can and cannot participate in anything related to Gentoo. |
12 |
|
13 |
The reason I had in mind is indeed the all-or-nothing security model |
14 |
for the publications (ebuilds is what I had in mind, I should have |
15 |
written "Everything I know in the Gentoo project...", sorry about that!) |
16 |
where even Copyright seems to have to be assigned to the foundation. |
17 |
|
18 |
|
19 |
> Gentoo projects have involved non-developers from time to time. The |
20 |
> documentation project even gives commit access to non-developers, |
21 |
|
22 |
Awesome! I'm really glad that I was wrong about that - but at the |
23 |
same time documentation tends to serve a bootstrapping function, |
24 |
and thus matter less over time. |
25 |
|
26 |
|
27 |
> and arch testers have elevated privileges in bugzilla. |
28 |
|
29 |
I should have included bugzilla among mailing lists+IRC, users can |
30 |
indeed also have elevated privileges on IRC, but never equal to |
31 |
developers. It is radical exclusion and I'm reminded of it every |
32 |
time the #gentoo-dev channel mode catches my eye, painfully so if |
33 |
there's a discussion I could perhaps contribute to. Most of the time |
34 |
it is easy enough to say something privately to a relevant developer, |
35 |
but that's still very different from actual participation. |
36 |
|
37 |
|
38 |
> The way our current portage tree is set up basically forces us into an |
39 |
> all-or-nothing security model for commit access - we don't have layers |
40 |
> of integration testing to protect users from errors or abuses. |
41 |
> |
42 |
> Proxy maintainership is one way around this. |
43 |
|
44 |
I considered mentioning it but I didn't because I think it's clear to |
45 |
everyone that it is indeed a workaround. |
46 |
|
47 |
|
48 |
> I think there are many here who would love to see more non-developer |
49 |
> contribution. |
50 |
|
51 |
Yes, I am absolutely sure that this is the case! |
52 |
|
53 |
But even though my blanket statement was incorrect, I guess the fact |
54 |
that I was wrong about this even after using Gentoo fairly actively |
55 |
for nearly 10 years means that it is not so clear to users if they |
56 |
can actually contribute in easy ways, and partially hostile |
57 |
documentation of course doesn't help. |
58 |
|
59 |
|
60 |
> Suggestions are always welcome, and those willing to put in effort |
61 |
> to make the suggestions happen are probably even more welcome. |
62 |
|
63 |
I for one consider the portage tree and the tools around it to be |
64 |
Gentoo's core value so I think writes to it becoming more accessible |
65 |
is the number one suggestion. |
66 |
|
67 |
|
68 |
> Moving to git certainly won't hurt, but that won't automatically |
69 |
> change anything either. |
70 |
|
71 |
I disagree there - it automatically changes what is effortlessly |
72 |
doable thanks to existence of helpful tooling and it also changes |
73 |
intuitive expectations as far as workflow goes. |
74 |
|
75 |
I do think that a world-writable Gerrit instance in front of a |
76 |
portage git tree will actually suffice to dramatically increase |
77 |
user participation - and of course bring significant developer |
78 |
review workload along with it! :) |
79 |
|
80 |
Everyone knows I'd like to see that happen, and I know that it is |
81 |
being worked on - I'm not in a hurry, but even so you're right that |
82 |
it still does not change the fact that only developers can submit |
83 |
commits from Gerrit into portage. |
84 |
|
85 |
As I already wrote I think there are both significant pros and cons |
86 |
to the developer-only approach, and because of how powerful and |
87 |
flexible Gentoo is there's no easy solution. |
88 |
|
89 |
As a case in point, TomWij made a mistake for an arch he rarely if |
90 |
ever uses. Gentoo is complex and also wonderful, and that means that |
91 |
contributing in the general case is not very easy. |
92 |
|
93 |
Simplifying the common case of x86/amd64 revbump (a world-writable Gerrit) |
94 |
will lead to more contribution, but what about the corner cases - it's |
95 |
impossible to know if I've actually tested my new ebuild on hppa if I |
96 |
just copypaste the old ebuild. I shouldn't need to communicate my |
97 |
testing out-of-band in a bugzilla or whatever and a thought I just |
98 |
had is that KEYWORDS may perhaps need higher temporal resolution than |
99 |
existing once per file.ebuild.. OTOH I don't think it's a good idea |
100 |
to require post-processing of the entire gentoo-x86 worktree to make |
101 |
it usable for portage. Tricky. |
102 |
|
103 |
|
104 |
//Peter |