diff options
1 files changed, 30 insertions, 35 deletions
diff --git a/www/policy/PolicyOnPolicy.html b/www/policy/PolicyOnPolicy.html
index c4d7bfa..be0ff2f 100644
--- a/www/policy/PolicyOnPolicy.html
+++ b/www/policy/PolicyOnPolicy.html
@@ -40,51 +40,44 @@ th {
<table width="100%">
-<td> PoP </td>
-<td> </td>
-<td width="20%"> Iang </td>
-<td> POLICY&nbsp;<a href="">p200800204.1</a> </td>
-<td> </td>
- 20080309
+<td>Name: PoP <a style="color: steelblue" href="">COD1</a><br />
+Status: POLICY&nbsp;<a href="">p20080204.1</a>, DRAFT&nbsp;<a href="">p20130223</a><br />
+Editor: Iang 20080309<br />
+Changes: <!-- span class="change">20100507, 20130223</span --><br />
+Licence: <a style="color: steelblue" href="" title="this document is Copyright &copy; CAcert Inc., licensed openly under CC-by-sa with all disputes resolved under DRP. More at" > CC-by-sa+DRP </a>
+<td align="right">
+ <a href=""><img src="images/cacert-policy.png" alt="PoP Status - POLICY" height="31" width="88" style="border-style: none;" /></a><br />
+ <a href=""><img src="images/cacert-draft.png" alt="PoP Status - DRAFT" height="31" width="88" style="border-style: none;" /></a>
-<td> COD1 </td>
-<td> </td>
-<td> </td>
-<td> </td>
-<td > <b>Policy&nbsp;on&nbsp;Policy</b> </td>
-<td> </td>
+<p><br /></p>
-<h2> 0. Preliminaries </h2>
+<h1> Policy&nbsp;on&nbsp;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 [policy] mail list forum.
+ within the open <span class="strike">[policy] mail list forum.</span> <span class="change">CAcert Policy Group <a href=""> mail list forum</a></span>.
-<h2> 1. Scope and Purpose </h2>
+<h2 id="s1"> 1. Scope and Purpose </h2>
+<p id="s1.1">
This policy documents and controls the process by which
CAcert creates and promulgates policies.
+<p id="s1.2">
The policy covers itself.
The policy replaces prior ones.
@@ -94,42 +87,44 @@ the policy is part of the Configuration-Control Specification
and also documents part of the CCS.
+<p id="s1.3">
The policies so created are generally binding on
-CAcert, registered users and related parties.
+<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>.
+<p id="s1.4">
The Policy Officer manages all policies
and the policy group.
The policy group is formed on the open mailing list
-known as [policy], and is to be open to all
+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> 2. Basic Model </h2>
+<h2 id="s2"> 2. Basic Model </h2>
+<p id="s2.1">
The basic concept was drawn from the IETF model.
+<p id="s2.2">
Policies are documented.
Documents start as <i>Work-In-Progress</i>, move through to
<i>DRAFT</i> and finalise in <i>POLICY</i> status.
+<p id="s2.3">
Decisions are taken by "Rough Consensus."
A vote may be called to clarify.
+<p id="s2.4">
Documents should include a minimum of information
in a standardised format managed by the Documentation Officer: