Gentoo Archives: gentoo-dev

From: Alec Warner <antarus@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Getting the general dev opinion ("Meinungsbild") on some feature
Date: Sun, 20 Jan 2013 21:00:19
Message-Id: CAAr7Pr8ODR3BxWQ7X=1qA+fdGy7Qicsy9_WAPkJ15Ny=p56qTw@mail.gmail.com
In Reply to: Re: [gentoo-dev] Getting the general dev opinion ("Meinungsbild") on some feature by "Andreas K. Huettel"
1 On Sun, Jan 20, 2013 at 9:32 AM, Andreas K. Huettel
2 <dilfridge@g.o> wrote:
3 > Am Sonntag, 20. Januar 2013, 10:39:58 schrieb Rich Freeman:
4 >>
5 >> What's the point? I don't think democracy is the best way to handle
6 >> these sorts of things.
7 >
8 > LOL. Yeah, but haven't we tried to give ourselves rules that at least resemble
9 > it?
10 >
11 > If I wanted to find out expert opinions and act on that, I'd directly ask a
12 > couple of people on IRC that I consider knowledgeable, and then directly
13 > follow their advice. No mailing list need be involved. This would be
14 > effective, most likely technologically correct, and fast. It would also cause
15 > major $hitstorms, since every developer knows best about a lot of things, and
16 > since a lot of people would understandably feel bypassed. I would lose commit
17 > privileges quite fast.
18
19 I think it is more difficult to lose commit privs than you think.
20 There are lots of warning signs. People being pissed off does not
21 equal getting your privs revoked. You do that for making horrific
22 technical errors; generally speaking.
23
24 >
25 > On the other hand, if I want to do the ultimate "right thing" in a community
26 > sense, I ask on the list and let the discussion develop. I get a lot of
27 > opinions. Some of these I consider more, some less sensible; some of these are
28 > better, some less well informed. On most issues, even well-informed people
29 > will have different opinions - sometimes things are just a matter of personal
30 > taste. Getting a real unanimous vote is impossible. I wait for everyone to
31 > read his mail; we've already heard that 72h is by far not enough time. (Half a
32 > year?) In the meantime the discussion has branched into a couple of topics,
33 > and most people have forgotten the original issue... Action may be taken on
34 > the day when debian stable has a newer glibc than gentoo (metaphorically
35 > speaking).
36
37 The general culture that I aspire to is one where developers take
38 responsibility for their work. If you make a change and break stuff,
39 you will lose trust. If you make a change and it goes well, you gain
40 trust. Trusted people are allowed more freedom (changes with perhaps
41 less discussion, or changes against an established consensus.) I think
42 listening to people is important. However listening to them does not
43 equal agreeing with them, or doing what they want. In the end you are
44 'in charge' of your change. People can make suggestions on how to do
45 things better, or offer advice against pitfalls. However in the end
46 you are the person doing the work, so the decisions are nominally
47 yours to make.
48
49 >
50 > We will in the end need a compromise that both gets things done and involves
51 > everyone that actively wants to be involved. (And yes, that means reading your
52 > mail!)
53 >
54 > --
55 > Andreas K. Huettel
56 > Gentoo Linux developer
57 > dilfridge@g.o
58 > http://www.akhuettel.de/