cacert/cacert-policies
9
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

a set of suggested changes taken from CCS work

Browse source 
git-svn-id: http://svn.cacert.org/CAcert/Policies@1896 14b1bab8-4ef6-0310-b690-991c95c89dfd
This commit is contained in:
Ian Grigg 2010-05-07 14:54:15 +00:00
parent 462d80109b
commit a47ed49998
1 changed files with 80 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

90
PolicyOnPolicy.html
View file

@ -1,8 +1,58 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8" />
<title>Policy on Policy</title>
<style type="text/css"> <!-- only for WIP -->
<!--
body {
font-family : verdana, helvetica, arial, sans-serif;
}
<html> th {
<head><title>Policy on Policy</title></head> text-align : left;
<body> }
.q {
color : green;
font-weight: bold;
text-align: center;
font-style:italic;
}
.change {
color : blue;
font-weight: bold;
}
.strike {
color : blue;
text-decoration:line-through;
}
-->
</style>
</head>
<body lang="en-GB">
<p>
<center>
<big>
<br><b>WARNING:</b><br />
The proper policy document is located<br />
<a href="//www.cacert.org/policy/PolicyOnPolicy.php">
on the CAcert website </a>.<br />
</big></b />
This document is a <b>working draft</b> to include<br />
future revisions only, and is currently<br />
only relevant for the [policy] group.<br />
Suggested <span class="change">additions in BLUE</span>, <span class="strike">strikes in blue<span>.<br />
</center>
Iang <span class="change">20100507</span>: fixed two errors being cacert-policy and 1.3 terminology.<br />
Iang <span class="change">20100507</span>: incorporated suggestions from CCS - 2.3, 5.4, 6.5<br />
</p>
<hr />
<table width="100%"> <table width="100%">
@ -13,10 +63,10 @@
</tr> </tr>
<tr> <tr>
<td> POLICY&nbsp;<a href="http://wiki.cacert.org/wiki/PolicyDecisions">p200800204.1</a> </td> <td> POLICY&nbsp;<a href="//wiki.cacert.org/wiki/PolicyDecisions">p200800204.1</a> </td>
<td> </td> <td> </td>
<td> <td>
20080309 20080309<span class="change">, 20100507</span>
</td> </td>
</tr> </tr>
@ -39,7 +89,7 @@
<p> <p>
Policy on Policy adopts the IETF model of Policy on Policy adopts the IETF model of
'rough consensus' to create CAcert documents 'rough consensus' to create CAcert documents
within the open [policy] mail list forum. within the open [<span class="change">cacert-</span>policy] mail list forum.
</p> </p>
@ -64,7 +114,9 @@ and also documents part of the CCS.
<p> <p>
1.3 1.3
The policies so created are generally binding on 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> </p>
<p> <p>
@ -72,7 +124,7 @@ CAcert, registered users and related parties.
The Policy Officer manages all policies The Policy Officer manages all policies
and the policy group. and the policy group.
The policy group is formed on the open mailing list The policy group is formed on the open mailing list
known as [policy], and is to be open to all known as [<span class="change">cacert-</span>policy], and is to be open to all
Community Members of CAcert. Community Members of CAcert.
</p> </p>
@ -109,6 +161,14 @@ date / time of the last edit,
Abstract. Abstract.
</p> </p>
<p class="change">
2.5
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.
</p>
<h2> 3. Work-In-Progress </h2> <h2> 3. Work-In-Progress </h2>
<p> <p>
@ -204,6 +264,15 @@ they may be included in the POLICY document,
but must be clearly indicated within as DRAFT not POLICY. but must be clearly indicated within as DRAFT not POLICY.
</p> </p>
<p class="change">
5.4
POLICY documents must be published on the CAcert website
in plain HTML format,
under the same change control as critical source code under
<a href="//svn.cacert.org/CAcert/Policies/SecurityPolicy.html">Security Policy</a>
SP => COD8.
</p>
<h2> 6. Open Process </h2> <h2> 6. Open Process </h2>
<p> <p>
@ -250,6 +319,7 @@ and clear licence by CAcert, Inc.
6.5 6.5
Mailing lists should be archived, Mailing lists should be archived,
and important meetings should be minuted. and important meetings should be minuted.
<span class="change">Policy Officer is to maintain a record of decisions.</span>
</p> </p>
<h2> 7. Disputes. </h2> <h2> 7. Disputes. </h2>
@ -278,7 +348,7 @@ to further group discussion.
7.4 7.4
The external avenue for disputes is to file a dispute The external avenue for disputes is to file a dispute
according to CAcert's according to CAcert's
<a href="http://www.cacert.org/policy/DisputeResolutionPolicy.php"> <a href="//www.cacert.org/policy/DisputeResolutionPolicy.php">
Dispute Resolution Policy</a> Dispute Resolution Policy</a>
DRP => COD7. DRP => COD7.
</p> </p>