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
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
|
<define-tag pagetitle>General Resolution: code of conduct</define-tag>
<define-tag status>F</define-tag>
# meanings of the <status> tag:
# P: proposed
# D: discussed
# V: voted on
# F: finished
# O: other (or just write anything else)
#use wml::debian::template title="<pagetitle>" BARETITLE="true" NOHEADER="true"
#use wml::debian::toc
#use wml::debian::votebar
<h1><pagetitle></h1>
<toc-display />
# The Tags beginning with v are will become H3 headings and are defined in
# english/template/debian/votebar.wml
# all possible Tags:
# vdate, vtimeline, vnominations, vdebate, vplatforms,
# Proposers
# vproposer, vproposera, vproposerb, vproposerc, vproposerd,
# vproposere, vproposerf
# Seconds
# vseconds, vsecondsa, vsecondsb, vsecondsc, vsecondsd, vsecondse,
# vsecondsf, vopposition
# vtext, vtextb, vtextc, vtextd, vtexte, vtextf
# vchoices
# vamendments, vamendmentproposer, vamendmentseconds, vamendmenttext
# vproceedings, vmajorityreq, vstatistics, vquorum, vmindiscuss,
# vballot, vforum, voutcome
<vtimeline />
<table class="vote">
<tr>
<th>Proposal and amendment</th>
<td>Wednesday, 12th February 2014</td>
<td></td>
</tr>
<tr>
<th>Discussion Period:</th>
<td>Monday, 10th March, 2014</td>
<td></td>
</tr>
<tr>
<th>Voting Period:</th>
<td>Monday, April 14<sup>st</sup>, 00:00:00 UTC, 2014</td>
<td>Sunday, April 27<sup>th</sup>, 23:59:59 UTC, 2014</td>
</tr>
</table>
<vproposer />
<p>Wouter Verhelst [<email wouter@debian.org>]
[<a href='https://lists.debian.org/debian-vote/2014/02/msg00002.html'>text of proposal</a>]
[<a href='https://lists.debian.org/debian-vote/2014/03/msg00149.html'>Accepting amendement</a>]
[<a href='https://lists.debian.org/debian-vote/2014/04/msg00005.html'>Call for vote</a>]
</p>
<vseconds />
<ol>
<li>Andrew Starr-Bochicchio [<email asb@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/02/msg00007.html'>mail</a>] </li>
<li>Neil McGovern [<email neilm@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00112.html'>mail</a>] </li>
<li>Thijs Kinkhorst [<email thijs@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00115.html'>mail</a>] </li>
<li>Paul Tagliamonte [<email paultag@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00116.html'>mail</a>] </li>
<li>Ian Jackson [<email iwj@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00117.html'>mail</a>] </li>
<li>Sylvestre Ledru [<email sylvestre@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00120.html'>mail</a>] </li>
<li>Stuart Prescott [<email stuart@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00136.html'>mail</a>] </li>
<li>Lars Wirzenius [<email lars@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00146.html'>mail</a>] </li>
</ol>
<vtext />
<h3>Choice 1: Accept CoC, DPL can update it</h3>
<ol>
<li>The Debian project decides to accept a code of conduct for
participants to its mailinglists, IRC channels, and other modes of
communication within the project.
<li>Updates to this code of conduct should be made by the DPL or the
DPL's delegates after consultation with the project, or by the Debian
Developers as a whole through the general resolution procedure.
<li>The initial text of the code of conduct follows, in markdown format.
</ol>
<hr />
<vamendmentproposera />
<p>Neil McGovern [<email neilm@debian.org>]
[<a href='https://lists.debian.org/debian-vote/2014/03/msg00113.html'>Text of original amendements</a>]
[<a href='https://lists.debian.org/debian-vote/2014/03/msg00160.html'>Accepting amendements</a>]
[<a href='https://lists.debian.org/debian-vote/2014/03/msg00166.html'>confirm accepting amendements</a>]
</p>
<vamendmentsecondsa />
<ol>
<li>Thijs Kinkhorst [<email thijs@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00115.html'>mail</a>] </li>
<li>Paul Tagliamonte [<email paultag@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00116.html'>mail</a>] </li>
<li>Sylvestre Ledru [<email sylvestre@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00120.html'>mail</a>] </li>
<li>Stuart Prescott [<email stuart@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00136.html'>mail</a>] </li>
<li>Lars Wirzenius [<email lars@debian.org>] [<a href='https://lists.debian.org/debian-vote/2014/03/msg00146.html'>mail</a>] </li>
</ol>
<vamendmenttexta />
<h3>Choice 2: Accept CoC, updates via GR</h3>
<ol>
<li>The Debian project decides to accept a code of conduct for
participants to its mailinglists, IRC channels, and other modes of
communication within the project.
<li>Updates to this code of conduct should follow the normal GR
procedure. However, the DPL (or the DPL's delegates) can add or
remove links to other documents in the "Further reading" section
after consultation with the project and without requiring a GR.
<li>The initial text of the code of conduct follows, in markdown format.
</ol>
<hr />
<h3>Initial text of the code of conduct</h3>
<pre>
\# Debian Code of Conduct
\## Be respectful
In a project the size of Debian, inevitably there will be people with
whom you may disagree, or find it difficult to cooperate. Accept that,
but even so, remain respectful. Disagreement is no excuse for poor
behaviour or personal attacks, and a community in which people feel
threatened is not a healthy community.
\## Assume good faith
Debian Contributors have many ways of reaching our common goal of a
[free](https://www.debian.org/intro/free) operating system which may
differ from your ways. Assume that other people are working towards this
goal.
Note that many of our Contributors are not native English speakers or
may have different cultural backgrounds
\## Be collaborative
Debian is a large and complex project; there is always more to learn
within Debian. It's good to ask for help when you need it. Similarly,
offers for help should be seen in the context of our shared goal of
improving Debian.
When you make something for the benefit of the project, be willing to
explain to others how it works, so that they can build on your work to
make it even better.
\## Try to be concise
Keep in mind that what you write once will be read by hundreds of
persons. Writing a short email means people can understand the
conversation as efficiently as possible. When a long explanation is
necessary, consider adding a summary.
Try to bring new arguments to a conversation so that each mail adds
something unique to the thread, keeping in mind that the rest of the
thread still contains the other messages with arguments that have
already been made.
Try to stay on topic, especially in discussions that are already fairly
large.
\## Be open
Most ways of communication used within Debian allow for public and
private communication. As per paragraph three of the [social
contract](https://www.debian.org/social_contract), you should preferably
use public methods of communication for Debian-related messages, unless
posting something sensitive.
This applies to messages for help or Debian-related support, too; not
only is a public support request much more likely to result in an answer
to your question, it also makes sure that any inadvertent mistakes made
by people answering your question will be more easily detected and
corrected.
\## In case of problems
While this code of conduct should be adhered to by participants, we
recognize that sometimes people may have a bad day, or be unaware of
some of the guidelines in this code of conduct. When that happens, you may
reply to them and point out this code of conduct. Such messages may be
in public or in private, whatever is most appropriate. However,
regardless of whether the message is public or not, it should still
adhere to the relevant parts of this code of conduct; in particular, it
should not be abusive or disrespectful. Assume good faith; it is more
likely that participants are unaware of their bad behaviour than that
they intentionally try to degrade the quality of the discussion.
Serious or persistent offenders will be temporarily or permanently
banned from communicating through Debian's systems. Complaints should be
made (in private) to the administrators of the Debian communication
forum in question. To find contact information for these administrators,
please see [the page on Debian's organizational
structure](https://www.debian.org/intro/organization)
\# Further reading
Some of the links in this section do not refer to documents that are
part of this code of conduct, nor are they authoritative within Debian.
However, they all do contain useful information on how to conduct
oneself on our communication channels.
- Debian has a [diversity statement](https://www.debian.org/intro/diversity)
- The [Debian Community Guidelines](http://people.debian.org/~enrico/dcg/)
by Enrico Zini contain some advice on how to communicate effectively.
- The [Mailing list code of
conduct](https://www.debian.org/MailingLists/#codeofconduct) is useful for
advice specific to Debian mailing lists
</pre>
<vquorum />
<p>
With the current list of <a href="vote_002_quorum.log">voting
developers</a>, we have:
</p>
<pre>
#include 'vote_002_quorum.txt'
</pre>
#include 'vote_002_quorum.src'
<vstatistics />
<p>
For this GR, like always,
# <a href="https://vote.debian.org/~secretary/codeofconduct/">statistics</a>
<a href="suppl_002_stats">statistics</a>
will be gathered about ballots received and
acknowledgements sent periodically during the voting
period.
Additionally, the list of voters will be
recorded. Also, the tally
sheet will also be made available to be viewed.
Additionally, the list of <a
href="vote_002_voters.txt">voters</a> will be
recorded. Also, the <a href="vote_002_tally.txt">tally
sheet</a> will also be made available to be viewed.
</p>
<vmajorityreq />
<p>
The proposal needs simple majority
</p>
#include 'vote_002_majority.src'
<voutcome />
#include 'vote_002_results.src'
<hrline />
<address>
<a href="mailto:secretary@debian.org">Debian Project Secretary</a>
</address>
|
