Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: "Michał Górny" <mgorny@g.o>
Cc: gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] GLEP RFC: Third-party contributions
Date: Thu, 27 Oct 2016 13:42:32
Message-Id: CAGfcS_=wtpUPcmoJzkGnKxRNscyzrZerrDGcD0=gf3DQYEy-=Q@mail.gmail.com
In Reply to: Re: [gentoo-dev] GLEP RFC: Third-party contributions by "Michał Górny"
1 On Thu, Oct 27, 2016 at 9:13 AM, Michał Górny <mgorny@g.o> wrote:
2 > On Thu, 27 Oct 2016 07:07:20 -0400
3 > Rich Freeman <rich0@g.o> wrote:
4 >
5 >>
6 >> I think this reflects reality. You can submit all the patches you
7 >> want via bugzilla but it isn't like we punish developers for not
8 >> getting around to accepting them, unless they're completely inactive
9 >> Gentoo-wide.
10 >
11 > I disagree here. I dare say that Bugzilla is obligatory for all
12 > developers (they get an account there during recruitment, after all).
13 > I agree they aren't required to accept patches but if a developer
14 > outright ignores all attempts of communication, you know what needs to
15 > be done.
16 >
17
18 Recruit more maintainers or treeclean the package if it is a blocker?
19
20 While I don't really care for the whole passive-aggressive thing that
21 some seem to enjoy, mere inaction by a volunteer in certain areas is a
22 hard problem to deal with, because if they're making positive
23 contributions in others it is hard to demand that they make a positive
24 contribution in an area that we choose.
25
26 I get that being met with silence is highly frustrating, and I've been
27 on the receiving end of it. Still, often the best solution isn't to
28 try to force somebody to do things our way, but to try to encourage
29 others to join in so that we have somebody to work with who is willing
30 to do it our way.
31
32 That is of course what this GLEP is all about.
33
34 >
35 > To be honest, after writing it all down, I started to get the feeling
36 > it isn't necessary after all. The initial idea (and what motivation was
37 > supposed to mean) was that all previous attempts failed because they
38 > either tried to be too specific, force too many style rules or just
39 > never got necessary 'global' to reach all affected parties.
40 >
41 > I'd dare say this GLEP ended up confirming 'third party contributions'
42 > are not that special, we don't need special teams to handle them or
43 > special rules to cover them.
44 >
45 > So yes, it would probably be enough to put such a simple statement
46 > somewhere. The problem is: where? ;-) GLEP seemed like a
47 > straightforward solution to make it global.
48 >
49
50 I think that is a completely fair question.
51
52 I wouldn't be hesitant to strongly promote a specific style,
53 especially if it isn't mandatory. Convention over configuration and
54 all that.
55
56 As far as promotion goes, I think something on this page might help:
57 https://gentoo.org/get-involved/contribute/
58
59 Right now that is fairly bugzilla-centric. I think expanding it to
60 offer bugzilla as one option among many could be helpful. The current
61 page doesn't even mention gentoo-proxy-maintainers.
62
63 I do think that this is one of the areas where hasufell's concept of
64 making the 3rd-party workflow the main workflow could have helped.
65 Right now the people with commit rights mostly do things in a way that
66 it is awkward to feed 3rd-party contributions into.
67
68 So, maybe instead of a GLEP we need something in the style of a
69 contributor and committer workflow/guide that work very tightly
70 together. Then we generate some excitement on the committer side of
71 that so that people who stick their toes in the water don't have a bad
72 experience, and then we promote it to the public.
73
74 --
75 Rich

Replies

Subject Author
Re: [gentoo-dev] GLEP RFC: Third-party contributions "Michał Górny" <mgorny@g.o>