source code taken from cacert-20090625.tar.bz2
[cacert.git] / cacert / www / policy / PolicyOnPolicy.php
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2
3 <html>
4 <head><title>Policy on Policy</title></head>
5 <body>
6
7 <table width="100%">
8
9 <tr>
10 <td> PoP </td>
11 <td> </td>
12 <td width="20%"> Iang </td>
13 </tr>
14
15 <tr>
16 <td> POLICY&nbsp;<a href="http://wiki.cacert.org/wiki/PolicyDecisions">p200800204.1</a> </td>
17 <td> </td>
18 <td>
19 20080309
20 </td>
21 </tr>
22
23 <tr>
24 <td> COD1 </td>
25 <td> </td>
26 <td> </td>
27 </tr>
28
29
30 <tr>
31 <td> </td>
32 <td > <b>Policy&nbsp;on&nbsp;Policy</b> </td>
33 <td> </td>
34 </tr>
35
36 </table>
37
38 <h2> 0. Preliminaries </h2>
39 <p>
40 Policy on Policy adopts the IETF model of
41 'rough consensus' to create CAcert documents
42 within the open [policy] mail list forum.
43 </p>
44
45
46 <h2> 1. Scope and Purpose </h2>
47
48 <p>
49 1.1
50 This policy documents and controls the process by which
51 CAcert creates and promulgates policies.
52 </p>
53
54 <p>
55 1.2
56 The policy covers itself.
57 The policy replaces prior ones.
58 For Audit purposes,
59 the policy is part of the Configuration-Control Specification
60 ("CCS", <a href="http://rossde.com/CA_review/CA_review_A.html#A1">DRC_A.1</a>)
61 and also documents part of the CCS.
62 </p>
63
64 <p>
65 1.3
66 The policies so created are generally binding on
67 CAcert, registered users and related parties.
68 </p>
69
70 <p>
71 1.4
72 The Policy Officer manages all policies
73 and the policy group.
74 The policy group is formed on the open mailing list
75 known as [policy], and is to be open to all
76 Community Members of CAcert.
77 </p>
78
79 <h2> 2. Basic Model </h2>
80
81 <p>
82 2.1
83 The basic concept was drawn from the IETF model.
84 </p>
85
86 <p>
87 2.2
88 Policies are documented.
89 Documents start as <i>Work-In-Progress</i>, move through to
90 <i>DRAFT</i> and finalise in <i>POLICY</i> status.
91 </p>
92
93 <p>
94 2.3
95 Decisions are taken by "Rough Consensus."
96 A vote may be called to clarify.
97 </p>
98
99 <p>
100 2.4
101 Documents should include a minimum of information
102 in a standardised format managed by the Documentation Officer:
103 the Title,
104 short name,
105 Document Status,
106 date the Status was reached,
107 Editor,
108 date / time of the last edit,
109 Abstract.
110 </p>
111
112 <h2> 3. Work-In-Progress </h2>
113
114 <p>
115 3.1
116 An Editor is identified.
117 This person is responsible for
118 drafting the document, following the consensus of the policy group.
119 </p>
120
121 <p>
122 3.2
123 The Policy Officer resolves minor disputes and keeps order.
124 </p>
125
126 <p>
127 3.3
128 The mail list of the policy group
129 is used as the primary debating
130 forum. A sub-group may be formed,
131 but decision-taking
132 should be visible on the main group.
133 </p>
134
135 <p>
136 3.4
137 Documents start with the status of
138 "Work-In-Progress" or WIP for short.
139 </p>
140
141
142 <h2> 4. DRAFT status </h2>
143
144 <p>
145 4.1
146 On completion, a document moves to DRAFT status.
147 </p>
148
149 <p>
150 4.2
151 A DRAFT is a policy-in-effect for the Community and is
152 to be distributed and treated as such.
153 </p>
154
155 <p>
156 4.3
157 As far as the Community is concerned, the DRAFT is policy.
158 Challenges and concerns can be addressed to the policy group,
159 and policy group discussions on a DRAFT
160 may be presented in Dispute Resolution.
161 </p>
162
163 <p>
164 4.4
165 Revisions of DRAFTs
166 must be treated as decisions on the policy group.
167 </p>
168
169 <p>
170 4.5
171 The period of the DRAFT status is announced widely,
172 which should be at least a month and no longer than a year.
173 </p>
174
175 <p>
176 4.6
177 During the period of DRAFT,
178 CAcert Inc. retains a veto over
179 policies that effect the running of CAcert Inc.
180 </p>
181
182
183 <h2> 5. POLICY status </h2>
184 <p>
185 5.1
186 After DRAFT period has elapsed with no revision beyond
187 minor and editorial changes,
188 there should be a decision
189 to move the document from
190 DRAFT to POLICY status.
191 </p>
192
193 <p>
194 5.2
195 Once POLICY, the Community may only challenge the document
196 in Dispute Resolution.
197 </p>
198
199 <p>
200 5.3
201 Policy group may propose changes to a POLICY document
202 in order to update it. When changes move to DRAFT status,
203 they may be included in the POLICY document,
204 but must be clearly indicated within as DRAFT not POLICY.
205 </p>
206
207 <h2> 6. Open Process </h2>
208
209 <p>
210 6.1
211 All policy discussions and documents should be open
212 processes. There should be a fair chance for
213 the Community
214 to have their views heard.
215 Rough Consensus is the working metric.
216 </p>
217
218 <p>
219 6.2
220 Contributions to
221 formally controlled documents such as Policies
222 are transferred fully to CAcert Inc.
223 Copyrights
224 and similar intellectual property rights
225 required to incorporate the Contribution
226 are either transferred to CAcert Inc, or,
227 are issued and contributed under free,
228 open, non-restrictive,
229 irrevocable, exclusive,
230 and clear licence to CAcert Inc.
231 In all cases, CAcert Inc licenses the
232 contributions back to the community
233 under an open licence.
234 </p>
235
236 <p>
237 6.3
238 Contributors declare any conflicts of interest.
239 </p>
240
241 <p>
242 6.4
243 Policies should be issued under free, open,
244 non-restrictive,
245 irrevocable, non-exclusive,
246 and clear licence by CAcert, Inc.
247 </p>
248
249 <p>
250 6.5
251 Mailing lists should be archived,
252 and important meetings should be minuted.
253 </p>
254
255 <h2> 7. Disputes. </h2>
256
257 <p>
258 7.1
259 Any questions not resolved by these rules
260 may be voted on in the policy group, or
261 may be dealt with in Dispute Resolution.
262 </p>
263
264 <p>
265 7.2
266 The Policy Officer may decide a tight vote in a minor matter only.
267 Failure of Rough Consensus may be declared by
268 dissenting members.
269 </p>
270
271 <p>
272 7.3
273 Matters unresolved refer back
274 to further group discussion.
275 </p>
276
277 <p>
278 7.4
279 The external avenue for disputes is to file a dispute
280 according to CAcert's
281 <a href="http://www.cacert.org/policy/DisputeResolutionPolicy.php">
282 Dispute Resolution Policy</a>
283 DRP => COD7.
284 </p>
285
286 </body>
287 </html>