bug 1131: Updated Policies based on new versions send by Policy Officer
[cacert-devel.git] / www / policy / PolicyOnPolicy.html
1 <!DOCTYPE html>
2 <html>
3 <head>
4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" lang="en">
5 <title>Policy on Policy</title>
6 <style type="text/css">
7 <!--
8 body {
9 font-family : verdana, helvetica, arial, sans-serif;
10 }
11
12 th {
13 text-align : left;
14 }
15
16 .comment {
17 color : steelblue;
18 }
19 .q {
20 color : green;
21 font-weight: bold;
22 text-align: center;
23 font-style:italic;
24 }
25 -->
26 </style>
27 </head>
28 <body>
29
30 <div class="comment">
31
32 <table width="100%">
33
34 <tbody>
35 <tr>
36
37 <td rowspan="2">
38 Name: PoP <a style="color: steelblue" href="https://svn.cacert.org/CAcert/Policies/ControlledDocumentList.html">COD1</a>
39 <br>
40 Status: POLICY&nbsp;<a href="https://wiki.cacert.org/PolicyDecisions#p20140731">p20140731</a>
41 <br>
42 Editor: Iang 20080309
43 <br>
44 Changes: 20100507, 20130223, 20140731
45 <br>
46 Licence: <a style="color: steelblue" href="https://wiki.cacert.org/Policy#Licence" title="this document is Copyright © 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>
47 <br>
48 </td>
49
50 <td align="right" valign="top">
51 <a href="https://www.cacert.org/policy/PolicyOnPolicy.php">
52 <img src="images/cacert-policy.png" alt="CCA Status - POLICY" style="border-style: none;" height="31" width="88">
53 </a>
54 </td>
55 </tr>
56 </tbody>
57 </table>
58 </div>
59
60 <p>
61 <br>
62 </p>
63
64 <h1> Policy&nbsp;on&nbsp;Policy </h1>
65
66
67
68 <h2 id="g0.1">Preliminaries </h2>
69 <p>
70 Policy on Policy adopts the IETF model of
71 'rough consensus' to create CAcert documents
72 within the open CAcert Policy Group <a href="https://lists.cacert.org/wws/info/cacert-policy"> mail list forum</a>.
73 </p>
74
75
76 <h2 id="g0.2">Scope and Purpose </h2>
77
78 <p id="s1.1">
79 1.1
80 This policy documents and controls the process by which
81 CAcert creates and promulgates policies.
82 </p>
83
84 <p id="s1.2">
85 1.2
86 The policy covers itself.
87 The policy replaces prior ones.
88 For Audit purposes,
89 the policy is part of the Configuration-Control Specification
90 ("CCS", <a href="http://rossde.com/CA_review/CA_review_A.html#A1">DRC_A.1</a>)
91 and also documents part of the CCS.
92 </p>
93
94 <p id="s1.3">
95 1.3
96 The policies so created are generally binding on
97 CAcert Inc., members under CAcert Community Agreement
98 (CCA =&gt; COD9) and other related parties under other agreements.
99 </p>
100
101 <p id="s1.4">
102 1.4
103 The Policy Officer manages all policies
104 and the policy group.
105 The policy group is formed on the open mailing list
106 known as CAcert Policy Group, and is to be open to all
107 Community Members of CAcert.
108 </p>
109
110
111 <h2 id="g0.3">Basic Model </h2>
112
113 <p id="s2.1">
114 2.1
115 The basic concept was drawn from the IETF model.
116 </p>
117
118 <p id="s2.2">
119 2.2
120 Policies are documented.
121 Documents start as <i>Work-In-Progress</i>, move through to
122 <i>DRAFT</i> and finalise in <i>POLICY</i> status.
123 </p>
124
125 <p id="s2.3">
126 2.3
127 Decisions are taken by "Rough Consensus."
128 A vote may be called to clarify.
129 </p>
130
131 <p id="s2.4">
132 2.4
133 Documents should include a minimum of information
134 in a standardised format managed by the Documentation Officer:
135 the Title,
136 short name,
137 Document Status,
138 date the Status was reached,
139 Editor,
140 date / time of the last edit,
141 Abstract.
142 </p>
143
144 <p id="s2.5">
145 2.5
146 Editors may make the following changes, where
147 it is clear that the change does not change the policy:</p>
148 <ul>
149 <li>
150 fixes to errors in grammar and spelling,
151 </li>
152 <li>
153 anchors, HTML errors, URLs &amp; formatting,
154 </li>
155 <li>
156 COD numbers and other references, and
157 </li>
158 <li>
159 other minutiae, as agreed under 2.3.
160 </li>
161 </ul>
162 <p>
163 Such changes to be notified to the policy group, and to be folded into effect, etc, without further ado.
164 </p>
165
166
167 <p id="s2.6">
168 2.6
169 Documents of lower status (work-in-progress or DRAFT)
170 must not be confusable with documents of higher status
171 (DRAFT or POLICY).
172 Copies should be eliminated where not being worked on.
173 </p>
174
175
176 <p id="s3.1">
177 3.1
178 An Editor is identified.
179 This person is responsible for
180 drafting the document, following the consensus of the policy group.
181 </p>
182
183 <p id="s3.2">
184 3.2
185 The Policy Officer resolves minor disputes and keeps order.
186 </p>
187
188 <p id="s3.3">
189 3.3
190 The mail list of the policy group
191 is used as the primary debating
192 forum. A sub-group may be formed,
193 but decision-taking
194 should be visible on the main group.
195 </p>
196
197 <p id="s3.4">
198 3.4
199 Documents start with the status of
200 "Work-In-Progress" or WIP for short.
201 </p>
202
203
204 <h2 id="g0.4">DRAFT status </h2>
205
206 <p id="s4.1">
207 4.1
208 On completion, a document moves to DRAFT status.
209 </p>
210
211 <p id="s4.2">
212 4.2
213 A DRAFT is a policy-in-effect for the Community and is
214 to be distributed and treated as such.
215 </p>
216
217 <p id="s4.3">
218 4.3
219 As far as the Community is concerned, the DRAFT is policy.
220 Challenges and concerns can be addressed to the policy group,
221 and policy group discussions on a DRAFT
222 may be presented in Dispute Resolution.
223 </p>
224
225 <p id="s4.4">
226 4.4
227 Revisions of DRAFTs
228 must be treated as decisions on the policy group.
229 </p>
230
231 <p id="s4.5">
232 4.5
233 The period of the DRAFT status is announced widely,
234 which should be at least a month and no longer than a year.
235 </p>
236
237 <p id="s4.6">
238 4.6
239 During the period of DRAFT,
240 CAcert Inc. retains a veto over
241 policies that effect the running of CAcert Inc.
242 </p>
243
244 <h2 id="g0.5">POLICY status </h2>
245 <p id="s5.1">
246 5.1
247 After DRAFT period has elapsed with no revision beyond
248 minor and editorial changes,
249 there should be a decision
250 to move the document from
251 DRAFT to POLICY status.
252 </p>
253
254 <p id="s5.2">
255 5.2
256 Once POLICY, the Community may only challenge the document
257 in Dispute Resolution.
258 </p>
259
260 <p id="s5.3">
261 5.3
262 Policy group may propose changes to a POLICY document
263 in order to update it. When changes move to DRAFT status,
264 they may be included in the POLICY document,
265 but must be clearly indicated within as DRAFT not POLICY.
266 </p>
267
268 <p id="s5.4">
269 5.4
270 POLICY documents are published on the CAcert website in plain HTML. Change control must be in place.
271 </p>
272
273 <h2 id="g0.6">Open Process </h2>
274
275 <p id="s6.1">
276 6.1
277 All policy discussions and documents should be open
278 processes. There should be a fair chance for
279 the Community
280 to have their views heard.
281 Rough Consensus is the working metric.
282 </p>
283
284 <p id="s6.2">
285 6.2
286 Contributions to
287 formally controlled documents such as Policies
288 are transferred fully to CAcert Inc.
289 Copyrights
290 and similar intellectual property rights
291 required to incorporate the Contribution
292 are either transferred to CAcert Inc, or,
293 are issued and contributed under free,
294 open, non-restrictive,
295 irrevocable, exclusive,
296 and clear licence to CAcert Inc.
297 In all cases, CAcert Inc licenses the
298 contributions back to the community
299 under an open licence.
300 </p>
301
302 <p id="s6.3">
303 6.3
304 Contributors declare any conflicts of interest.
305 </p>
306
307 <p id="s6.4">
308 6.4
309 Policies should be issued under free, open,
310 non-restrictive,
311 irrevocable, non-exclusive,
312 and clear licence by CAcert, Inc.
313 </p>
314
315 <p id="s6.5">
316 6.5
317 Mailing lists should be archived,
318 and important meetings should be minuted.
319 A record of decisions is to be maintained.
320 </p>
321
322 <h2 id="g0.7">Disputes. </h2>
323
324 <p id="s7.1">
325 7.1
326 Any questions not resolved by these rules
327 may be voted on in the policy group, or
328 may be dealt with in Dispute Resolution.
329 </p>
330
331 <p id="s7.2">
332 7.2
333 The Policy Officer may decide a tight vote in a minor matter only.
334 Failure of Rough Consensus may be declared by
335 dissenting members.
336 </p>
337
338 <p id="s7.3">
339 7.3
340 Matters unresolved refer back
341 to further group discussion.
342 </p>
343
344 <p id="s7.4">
345 7.4
346 The external avenue for disputes is to file a dispute
347 according to CAcert's
348 <a href="https://www.cacert.org/policy/DisputeResolutionPolicy.php">
349 Dispute Resolution Policy</a>
350 DRP =&gt; COD7.
351 </p>
352 </body>
353 </html>