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