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