summaryrefslogtreecommitdiff
path: root/www/policy/PolicyOnPolicy.html
blob: 56271b6147131341c59ceb96d0e83b8c742a013b (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
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
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8" lang="en">
 <title>Policy on Policy</title>
<style type="text/css">  <!-- only for WIP -->
<!--
body {
        font-family : verdana, helvetica, arial, sans-serif;
}

th {
        text-align : left;
}

.q {
        color : green;
        font-weight: bold;
        text-align: center;
        font-style:italic;
}

.change {
        color : blue;
        font-weight: bold;
}
.strike {
        color : blue;
        text-decoration:line-through;
}
.r {
    text-align : right;
}
-->
</style>

</head>
<body lang="en-GB">

<table width="100%">

<tr>
<td>Name: PoP <a style="color: steelblue" href="https://svn.cacert.org/CAcert/Policies/ControlledDocumentList.html">COD1</a><br />
Status: POLICY&nbsp;<a href="https://wiki.cacert.org/PolicyDecisions#p20080204.1">p20080204.1</a>, DRAFT&nbsp;<a href="https://wiki.cacert.org/PolicyDecisions#p20130223">p20130223</a><br />
Editor: Iang 20080309<br />
Changes: <!-- span class="change">20100507, 20130223</span --><br />
Licence: <a style="color: steelblue" href="https://wiki.cacert.org/Policy#Licence" title="this document is Copyright &copy; CAcert Inc., licensed openly under CC-by-sa with all disputes resolved under DRP.  More at wiki.cacert.org/Policy" > CC-by-sa+DRP </a>
</td>
<td align="right">
  <a href="https://www.cacert.org/policy/PolicyOnPolicy.html"><img src="images/cacert-policy.png" alt="PoP Status - POLICY" height="31" width="88" style="border-style: none;" /></a><br />
  <a href="https://www.cacert.org/policy/PolicyOnPolicy.html"><img src="images/cacert-draft.png" alt="PoP Status - DRAFT" height="31" width="88" style="border-style: none;" /></a>
</td>
</tr>


</table>


<p><br /></p>

<h1> Policy&nbsp;on&nbsp;Policy </h1>


<h2 id="s0"> 0. Preliminaries </h2>
<p>
    Policy on Policy adopts the IETF model of
    'rough consensus' to create CAcert documents
    within the open <span class="strike">[policy] mail list forum.</span> <span class="change">CAcert Policy Group <a href="https://lists.cacert.org/wws/info/cacert-policy"> mail list forum</a></span>.
</p>


<h2 id="s1"> 1. Scope and Purpose </h2>

<p id="s1.1">
1.1
This policy documents and controls the process by which
CAcert creates and promulgates policies.
</p>

<p id="s1.2">
1.2
The policy covers itself.
The policy replaces prior ones.
For Audit purposes,
the policy is part of the Configuration-Control Specification
("CCS", <a href="http://rossde.com/CA_review/CA_review_A.html#A1">DRC_A.1</a>)
and also documents part of the CCS.
</p>

<p id="s1.3">
1.3
The policies so created are generally binding on
<span class="strike">CAcert, registered users and related parties</span>
<span class="change">CAcert Inc., members under CAcert Community Agreement
(CCA => COD9) and other related parties under other agreements</span>.
</p>

<p id="s1.4">
1.4
The Policy Officer manages all policies
and the policy group.
The policy group is formed on the open mailing list
known as <span class="strike">[cacert-policy]</span> <span class="change">CAcert Policy Group</span>, and is to be open to all
Community Members of CAcert.
</p>

<h2 id="s2"> 2. Basic Model </h2>

<p id="s2.1">
2.1
The basic concept was drawn from the IETF model.
</p>

<p id="s2.2">
2.2
Policies are documented.
Documents start as <i>Work-In-Progress</i>, move through to
<i>DRAFT</i> and finalise in <i>POLICY</i> status.
</p>

<p id="s2.3">
2.3
Decisions are taken by "Rough Consensus."
A vote may be called to clarify.
</p>

<p id="s2.4">
2.4
Documents should include a minimum of information
in a standardised format managed by the Documentation Officer:
the Title,
short name,
Document Status,
date the Status was reached,
Editor,
date / time of the last edit,
Abstract.
</p>

<p class="change">
2.5
Editors may make the following changes, where
     it is clear that the change does not change the policy:</p>
<ul><li>
      <span class="change">fixes to errors in grammar and spelling,</span>
    </li><li>
      <span class="change">anchors, HTML errors, URLs &amp; formatting,</span>
    </li><li>
      <span class="change">COD numbers and other references, and</span>
    </li><li>
      <span class="change">other minutiae, as agreed under 2.3.</span>
    </li>
</ul>
<p class="change">
Such changes to be notified to the policy group, and to be folded into effect, etc, without further ado.
</p>


<p class="change">
2.6
Documents of lower status (work-in-progress or DRAFT)
must not be confusable with documents of higher status
(DRAFT or POLICY).
Copies should be eliminated where not being worked on.
</p>

<h2 id="s3"> 3. Work-In-Progress </h2>

<p id="s3.1">
3.1
An Editor is identified.
This person is responsible for
drafting the document, following the consensus of the policy group.
</p>

<p id="s3.2">
3.2
The Policy Officer resolves minor disputes and keeps order.
</p>

<p id="s3.3">
3.3
The mail list of the policy group
is used as the primary debating
forum. A sub-group may be formed,
but decision-taking
should be visible on the main group.
</p>

<p id="s3.4">
3.4
Documents start with the status of
"Work-In-Progress" or WIP for short.
</p>


<h2 id="s4"> 4. DRAFT status </h2>

<p id="s4.1">
4.1
On completion, a document moves to DRAFT status.
</p>

<p id="s4.2">
4.2
A DRAFT is a policy-in-effect for the Community and is
to be distributed and treated as such.
</p>

<p id="s4.3">
4.3
As far as the Community is concerned, the DRAFT is policy.
Challenges and concerns can be addressed to the policy group,
and policy group discussions on a DRAFT
may be presented in Dispute Resolution.
</p>

<p id="s4.4">
4.4
Revisions of DRAFTs
must be treated as decisions on the policy group.
</p>

<p id="s4.5">
4.5
The period of the DRAFT status is announced widely,
which should be at least a month and no longer than a year.
</p>

<p id="s4.6">
4.6
During the period of DRAFT,
CAcert Inc. retains a veto over
policies that effect the running of CAcert Inc.
</p>


<h2 id="s5"> 5. POLICY status </h2>
<p id="s5.1">
5.1
After DRAFT period has elapsed with no revision beyond
minor and editorial changes,
there should be a decision
to move the document from
DRAFT to POLICY status.
</p>

<p id="s5.2">
5.2
Once POLICY, the Community may only challenge the document
in Dispute Resolution.
</p>

<p id="s5.3">
5.3
Policy group may propose changes to a POLICY document
in order to update it.  When changes move to DRAFT status,
they may be included in the POLICY document,
but must be clearly indicated within as DRAFT not POLICY.
</p>

<p class="change">
5.4
POLICY documents are published on the CAcert website in plain HTML.  Change control must be in place.
</p>


<h2 id="s6"> 6. Open Process </h2>

<p id="s6.1">
6.1
All policy discussions and documents should be open
processes.  There should be a fair chance for
the Community
to have their views heard.
Rough Consensus is the working metric.
</p>

<p id="s6.2">
6.2
Contributions to
formally controlled documents such as Policies
are transferred fully to CAcert Inc.
Copyrights
and similar intellectual property rights
required to incorporate the Contribution
are either transferred to CAcert Inc, or,
are issued and contributed under free,
open, non-restrictive,
irrevocable, exclusive,
and clear licence to CAcert Inc.
In all cases, CAcert Inc licenses the
contributions back to the community
under an open licence.
</p>

<p id="s6.3">
6.3
Contributors declare any conflicts of interest.
</p>

<p id="s6.4">
6.4
Policies should be issued under free, open,
non-restrictive,
irrevocable, non-exclusive,
and clear licence by CAcert, Inc.
</p>

<p id="s6.5">
6.5
Mailing lists should be archived,
and important meetings should be minuted.
<span class="change">A record of decisions is to be maintained.</span>
</p>

<h2 id="s7"> 7. Disputes. </h2>

<p id="s7.1">
7.1
Any questions not resolved by these rules
may be voted on in the policy group, or
may be dealt with in Dispute Resolution.
</p>

<p id="s7.2">
7.2
The Policy Officer may decide a tight vote in a minor matter only.
Failure of Rough Consensus may be declared by
dissenting members.
</p>

<p id="s7.3">
7.3
Matters unresolved refer back
to further group discussion.
</p>

<p id="s7.4">
7.4
The external avenue for disputes is to file a dispute
according to CAcert's
<a href="https://www.cacert.org/policy/DisputeResolutionPolicy.html">
Dispute Resolution Policy</a>
DRP => COD7.
</p>
  <p><a href="http://validator.w3.org/check?uri=referer"><img
      src="images/valid-xhtml11-blue.png" alt="Valid XHTML 1.1" height="31" width="88" /></a></p>
</body>
</html>