Gentoo Archives: gentoo-dev

From: Mike Frysinger <vapier@g.o>
To: gentoo-dev@l.g.o
Cc: Aron Griffis <agriffis@g.o>
Subject: Re: [gentoo-dev] adding a code of conduct
Date: Tue, 04 Apr 2006 05:31:17
Message-Id: 200604040127.54134.vapier@gentoo.org
In Reply to: Re: [gentoo-dev] adding a code of conduct by Aron Griffis
1 On Monday 03 April 2006 19:35, Aron Griffis wrote:
2 > I disagree with fast-tracking this to any official Gentoo
3 > documentation.
4
5 i never used the word "fast" ... where did it come from ? maybe from the
6 sweet behind of yours ? (you're going to be at LWE this year right ?
7 mmmmmmmmmmmmmm)
8
9 > > Be considerate. Your work will be used by other people, and you in
10 > > turn will depend on the work of others. Any decision you make will
11 > > affect users and colleagues, and we expect you to take those
12 > > consequences into account when making decisions.
13 >
14 > All of this is obvious, except for who is "we"?
15
16 the Gentoo community ? your peers and loved ones ?
17
18 > > Be respectful. The Gentoo community and its members treat one
19 > > another with respect.
20 >
21 > Odd to make this declarative statement when it isn't true.
22
23 this document now exists because this statement isnt true ... this is one part
24 of a solution imo
25
26 > > Everyone can make a valuable contribution to Gentoo.
27 >
28 > They can? Making this kind of feel-good blanket statement just
29 > detracts from the rest of this document.
30
31 how so ? one of the critiques we have is that one jackass can turn off
32 users/potential devs simply by their abrasive behavior. another critique is
33 that some of us (i am guilty of this as well) of being too "snobbish" in
34 terms of who can actually make useful contributions (generally if you have an
35 @gentoo.org, that somehow "qualifies" you while those who do not are just
36 meat). i recognize i'm a bit of a dick and i'm trying to change.
37
38 > > We may not always agree, but disagreement is no excuse for
39 > > poor behaviour and poor manners. We might all experience some
40 > > frustration now and then, but we cannot allow that frustration to
41 > > turn into a personal attacks. It's important to remember that
42 > > a community where people feel uncomfortable or threatened is not
43 > > a productive one.
44 >
45 > This should be shortened to say just what it means: Developers will
46 > have more fun, be more productive, and create a better distribution if
47 > we concentrate on the issues instead of resorting to personal attacks.
48
49 i sort of like the longer winded version better ... really this paragraph
50 shouldnt have to exist at all, but since it does, i like the version that
51 spells out each detail clearly.
52
53 > > We expect members of the Gentoo community to be
54 > > respectful when dealing with other contributors as well as with
55 > > people outside the Gentoo project, and with users of Gentoo.
56 >
57 > Again, who is "we"?
58
59 see previous comment
60
61 > > Be collaborative. Gentoo and Free Software are about collaboration
62 > > and working together. Collaboration reduces redundancy of work done
63 > > in the Free Software world, and improves the quality of the software
64 > > produced. You should aim to collaborate with other Gentoo
65 > > maintainers, as well as with the upstream community that is
66 > > interested in the work you do. Your work should be done
67 > > transparently and patches from Gentoo should be given back to the
68 > > community when they are made, not just when the distribution
69 > > releases. If you wish to work on new code for existing upstream
70 > > projects, at least keep those projects informed of your ideas and
71 > > progress. It may not be possible to get consensus from upstream or
72 > > even from your colleagues about the correct implementation of an
73 > > idea, so don't feel obliged to have that agreement before you begin,
74 > > but at least keep the outside world informed of your work, and
75 > > publish your work in a way that allows outsiders to test, discuss
76 > > and contribute to your efforts.
77 >
78 > This part makes sense, I think... though I don't see the point of
79 > codifying it except to "throw the book" at the next Paludis. Frankly
80 > I think Ciaran did nothing wrong to restrict distribution on a project
81 > he didn't feel was ready for public consumption. It has always seemed
82 > to me like the overreactions were the problem.
83
84 err, i dont see this interpretation at all ... how would this affect the
85 Paludis work ? in anything, it codifies the work as being even "more" valid
86
87 really though, this paragraph is not targeted at the Paludis project or Ciaran
88 in any way ... not quite sure where this thought of yours is coming from
89 (somewhere underneath that beautiful hair of yours i imagine)
90
91 > > When you disagree, consult others. Disagreements, both political and
92 > > technical, happen all the time and the Gentoo community is no
93 > > exception. The important goal is not to avoid disagreements or
94 > > differing views but to resolve them constructively. You should turn
95 > > to the community and to the community process to seek advice and to
96 > > resolve disagreements. We have the Council, Infra, Devrel and Team
97 > > Leaders all of which help you decide the right course for Gentoo.
98 >
99 > What do you mean by "turn to the community and to the community
100 > process"? I'm not sure what that entails.
101
102 we have a couple "standard" means of opening community discussion. irc,
103 e-mail lists, forums, you name it.
104
105 > And I'm really not sure I understand what the last sentence means.
106
107 the idea is to provide some good examples of resources you can query for
108 feedback ... perhaps tweak the sentence a little ?
109
110 > > Repeated disruptive behaviors will be viewed as a security and
111 > > stability threat to Gentoo.
112 >
113 > Classic switching to the passive voice when the actor wishes to be
114 > distanced from the action.
115
116 please consider the document without these disciplinary related paragraphs as
117 they belong elsewhere
118 -mike
119 --
120 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] adding a code of conduct Jeroen Roovers <jer@g.o>