Diffstat (limited to 'www/policy/PolicyOnPolicy.html')
1 files changed, 347 insertions, 0 deletions
diff --git a/www/policy/PolicyOnPolicy.html b/www/policy/PolicyOnPolicy.html
new file mode 100644
@@ -0,0 +1,347 @@
+<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*/
+ font-family : verdana, helvetica, arial, sans-serif;
+ text-align : left;
+ color : green;
+ font-weight: bold;
+ text-align: center;
+ color : blue;
+ font-weight: bold;
+ color : blue;
+ text-align : right;
+<table style="width: 100%;">
+<td>Name: PoP <a style="color: steelblue" href="https://svn.cacert.org/CAcert/Policies/ControlledDocumentList.html">COD1</a><br />
+Status: POLICY <a href="https://wiki.cacert.org/PolicyDecisions#p20080204.1">p20080204.1</a>, DRAFT <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 © 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>
+ <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>
+<h1> Policy on Policy </h1>
+<h2 id="s0"> 0. Preliminaries </h2>
+ 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>.
+<h2 id="s1"> 1. Scope and Purpose </h2>
+This policy documents and controls the process by which
+CAcert creates and promulgates policies.
+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.
+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>.
+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.
+<h2 id="s2"> 2. Basic Model </h2>
+The basic concept was drawn from the IETF model.
+Policies are documented.
+Documents start as <i>Work-In-Progress</i>, move through to
+<i>DRAFT</i> and finalise in <i>POLICY</i> status.
+Decisions are taken by "Rough Consensus."
+A vote may be called to clarify.
+Documents should include a minimum of information
+in a standardised format managed by the Documentation Officer:
+date the Status was reached,
+date / time of the last edit,
+Editors may make the following changes, where
+ it is clear that the change does not change the policy:</p>
+ <span class="change">fixes to errors in grammar and spelling,</span>
+ <span class="change">anchors, HTML errors, URLs & formatting,</span>
+ <span class="change">COD numbers and other references, and</span>
+ <span class="change">other minutiae, as agreed under 2.3.</span>
+Such changes to be notified to the policy group, and to be folded into effect, etc, without further ado.
+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.
+<h2 id="s3"> 3. Work-In-Progress </h2>
+An Editor is identified.
+This person is responsible for
+drafting the document, following the consensus of the policy group.
+The Policy Officer resolves minor disputes and keeps order.
+The mail list of the policy group
+is used as the primary debating
+forum. A sub-group may be formed,
+should be visible on the main group.
+Documents start with the status of
+"Work-In-Progress" or WIP for short.
+<h2 id="s4"> 4. DRAFT status </h2>
+On completion, a document moves to DRAFT status.
+A DRAFT is a policy-in-effect for the Community and is
+to be distributed and treated as such.
+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.
+Revisions of DRAFTs
+must be treated as decisions on the policy group.
+The period of the DRAFT status is announced widely,
+which should be at least a month and no longer than a year.
+During the period of DRAFT,
+CAcert Inc. retains a veto over
+policies that effect the running of CAcert Inc.
+<h2 id="s5"> 5. POLICY status </h2>
+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.
+Once POLICY, the Community may only challenge the document
+in Dispute Resolution.
+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.
+POLICY documents are published on the CAcert website in plain HTML. Change control must be in place.
+<h2 id="s6"> 6. Open Process </h2>
+All policy discussions and documents should be open
+processes. There should be a fair chance for
+to have their views heard.
+Rough Consensus is the working metric.
+formally controlled documents such as Policies
+are transferred fully to CAcert Inc.
+and similar intellectual property rights
+required to incorporate the Contribution
+are either transferred to CAcert Inc, or,
+are issued and contributed under free,
+and clear licence to CAcert Inc.
+In all cases, CAcert Inc licenses the
+contributions back to the community
+under an open licence.
+Contributors declare any conflicts of interest.
+Policies should be issued under free, open,
+and clear licence by CAcert, Inc.
+Mailing lists should be archived,
+and important meetings should be minuted.
+<span class="change">A record of decisions is to be maintained.</span>
+<h2 id="s7"> 7. Disputes. </h2>
+Any questions not resolved by these rules
+may be voted on in the policy group, or
+may be dealt with in Dispute Resolution.
+The Policy Officer may decide a tight vote in a minor matter only.
+Failure of Rough Consensus may be declared by
+Matters unresolved refer back
+to further group discussion.
+The external avenue for disputes is to file a dispute
+according to CAcert's
+Dispute Resolution Policy</a>
+DRP => COD7.
+<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>