summaryrefslogtreecommitdiff
blob: b35d9759d5e8fd889f9d64b8259c667da5f9baf5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
\chapter{Code of Conduct}


\section{``Code of Conduct'', Mar. 2007}
Source: 
\url{
https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/council/ 
coc.xml?revision=1.2&view=markup}

\vspace*{1cm}

\begin{quote}
This document describes Gentoo's Code of Conduct for public communication fora,
as well as the action taken should it be broken.
\end{quote}

\subsection{Draft disclaimer}
This document is an ongoing work, subject to growth and revision as Gentoo 
grows and changes.

\subsection{Scope}

\paragraph{Joining and participation agreement}

Gentoo prides itself on being a community driven distribution that acts with 
the  best interest of the community at heart. Rules and regulations that keep us 
all  moving in a forward direction are a reality for a community of this size. 

This document describes Gentoo's Code of Conduct for public communication 
mediums,  who shall enforce said Code of Conduct, the action taken should the 
Code of  Conduct be broken, as well as the method for appeals. Questions about 
this document and its contents can be directed to the council at 
council@gentoo.org.

By joining and/or participating in the Gentoo community, you are stating that
you accept and agree to adhere to the rules listed below, even if you do not
explicitly state so.

\subsection{Behaviour and Consequences}

\paragraph{Acceptable behaviour}

Things that should be seen:
\begin{itemize}
 \item 
{\bf Be courteous.} Though respect is earned, it must start somewhere.      
    Respect someones right for their own opinion and acknowledge that they do    
   deserve a measure of politeness in your response.
\item
{\bf Give accurate information in the spirit of being helpful.}
\item
{\bf Respectfully disagree with or challenge other members.} The
    operative word here is respectfully.
\item
{\bf Using the correct forum for your post.} Bug reports and idle 
chatter
    do not belong on the gentoo-dev mailing list; discussion about a
    wide-ranging change to the tree probably does not belong on Bugzilla.
    Different fora will also have different standards of behaviour -- a joke
    that is perfectly acceptable on IRC will be taken differently when made on a
    mailing list.
\item
{\bf Admit the possibility of fault and respect different point of views.}
    Noone is perfect -- you will get things wrong occasionally. Don't be afraid
    to admit this. Similarly, while something may seem perfectly obvious to you,
    others may see it differently. 
\item
{\bf If you screw up, take responsibility for your actions.}
\end{itemize}

\paragraph{Unacceptable behaviour}

Gentoo developers have come together with a common purpose, to further the  
project. Conflicts will undoubtedly arise, and though you are encouraged to work 
through issues on your own, assistance is available as requested and as needed.

Deciding to suspend or ban someone isn't a decision to be taken lightly, but
sometimes it has to happen. Below is a list of things that could result in  
disciplinary action.

\begin{itemize}
 \item 
 {\bf Flaming and trolling.} What is trolling? You are deemed to be trolling 
      if you make comments intended to provoke an angry response from others. 
What      is flaming? Flaming is the act of sending or posting messages that are 
           deliberately hostile and insulting.
\item 
{\bf Posting/participating only to incite drama or negativity}
rather than
    to tactfully share information.
\item
{\bf Being judgmental, mean-spirited or insulting.} It is possible to
    respectfully challenge someone in a way that empowers without being          
     judgemental.
\item
{\bf Constantly purveying misinformation} despite repeated warnings.
\end{itemize}

\paragraph{Consequences}

Disciplinary action will be up to the descretion of the proctors. What is a  
proctor? A proctor is an official charged with the duty of maintaining good  
order. If discplinary measures are taken and the affected person wishes to  
appeal, appeals should be addressed to the Gentoo Council via email at 
council@gentoo.org. To prevent conflicts of interest, Council members may not 
perform the duties of a proctor.

If you perceive a breach of the Code of Conduct guidelines, let the proctors  
know. Though they will also be watching many of the public mediums for any  
problems, they can not be expected to catch everything.

The proctors will attempt to resolve the problem by talking to involved 
parties,  potentially issuing warnings if appropriate. If the problem repeats 
itself,  there are various options open to the proctors, including temporary or 
permanent  suspension of a person's ability to post to mailing lists, removal of 
Bugzilla  access, or in more severe cases suspension of developer privileges. 
Any action  of this sort will require consensus from at least three proctors.

\subsection{Summary}

If you are unsure whether or not something is OK to post/comment/etc,
assume it isn't, and reconsider whether you need to post it. Remember that posts
made to mailing lists are archived for perpetuity, and read by far more people
than will be actively involved in any one thread. A comment made in anger can
have far-reaching consequences that you might not have thought about at the 
time.

Remember, the moment you participate in a public discussion on Gentoo medium,
you have made yourself a representative of the Gentoo community. We hope that
you will not take this responsibility lightly, and will prove to be a positive
force in it.



\section{``CoC enforcement proposal'', by Donnie Berkholz, Nov. 2007}
\label{2007-11-dberkholz-coc}
Source: \agoref{gentoo-council}{cbfe572adb090dfba1cc004b1cca6979}
\index{Code of Conduct!enforcement}\index{project!proctors}
\index{developer!dberkholz}
\vspace*{1cm}


Consider this entire document a draft open to council discussion. I 
appreciate the people on the gentoo-project list who contributed to the 
discussion.

\paragraph{The problem}

My basic philosophy is: compliment in public, criticize in private. One 
of the problems with the proctors last time around was that their 
actions became too public, embarrassing the parties involved. Another 
problem with the proctors was that real action was not taken soon 
enough, and too long was spent talking. Real action in this context 
means that someone is temporarily blocked from posting to the relevant 
forum (mailing lists, IRC, forums), rather than sitting around talking. 
A third problem with the proctors was the difference in interpretation 
of the CoC within the group and with the council. It's particularly 
important to discriminate technical discussions from personal attacks 
and misconduct.

\paragraph{The conceptual solution}

A primary focus of CoC enforcement is deterrence from continued 
violation, so permanent action is unnecessary. Thus, what seems 
necessary is a way to take rapid, private, temporary action.

By making initial actions temporary (e.g., 6-12 hours in most cases), 
they can be taken rapidly with little negative consequence in the case 
of a mistake. The goal is to provide developers with a cooling-off 
period but allow them to rejoin the discussion with little loss. Since 
the actions are always private, the only reason other developers will 
learn about them is that either the affected developer or whoever took 
the action (the actor) leaked it. Leaks by the actor will be taken 
seriously as a CoC violation in their own right.

The basic idea behind the time frame is that the longer the action, the 
fewer people who can choose to take it. Perhaps only one or two people 
besides the council could decide to take any action longer than 12 
hours, which would severely impede a developer's ability to participate 
in a discussion.

Whoever's taking action also needs to have a similar interpretation of 
the CoC as the council, which is the problem that came up with the 
proctors. To ensure this, the council will need some kind of role in 
deciding who could take action. But we don't want to fall into the trap 
of writing down every little rule and every possible infraction; that 
just makes it easy to find loopholes.

\paragraph{The implementation}

One way to enable Gentoo to enforce the CoC with these ideas in mind is 
to create a highly selective team with only short-term abilities and a 
strong lead to ensure the team's actions fit the council's CoC 
interpretation. Adhering to the principles mentioned above is what 
discriminates between this group and the former proctors.

All this team's actions must be approved by the lead within a short time 
period or must be reverted. It's expected that many actions will range 
from 6-12 hours, so 12 hours seems like a reasonable time to require 
lead approval. Whenever the lead is unavailable, approval falls to the 
council. (Remember, two council members together can make decisions.)

The lead of this team must gain council approval for any action lasting 
3 or more days. To ensure that this process remains temporary, in no 
case can any action last longer than 7 days. These actions must also be 
forwarded on to devrel or userrel, depending on who's involved, and they 
will consider longer-term suspension or termination.

There is no conflict of interest between the council and this team's 
members, because the council is considered to have the best interests of 
Gentoo in mind. Developers can be members of both groups. The council 
must approve all members of this team, and it must reassess them 
annually to ensure they still interpret the CoC in the same way. 
Furthermore, the team's lead will be appointed by the council to further 
ensure a cohesive CoC interpretation.

It is expected that membership on this team will be highly selective and 
not all who wish to join will make the cut. The team will be limited to 
3 people for a probationary period so we don't get dumped in the deep 
end right away, and it will never have more than 5 people. Once 
appointed by the council, the team lead will choose applicants for the 
rest of the team to forward on for council approval.



\chapter{Stabilization}