You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
357 lines
7.5 KiB
HTML
357 lines
7.5 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" lang="en">
|
|
<title>Policy on Policy</title>
|
|
<style type="text/css">
|
|
<!--
|
|
body {
|
|
font-family : verdana, helvetica, arial, sans-serif;
|
|
}
|
|
|
|
th {
|
|
text-align : left;
|
|
}
|
|
|
|
.comment {
|
|
color : steelblue;
|
|
}
|
|
.q {
|
|
color : green;
|
|
font-weight: bold;
|
|
text-align: center;
|
|
font-style:italic;
|
|
}
|
|
-->
|
|
</style>
|
|
</head>
|
|
<body>
|
|
|
|
<div class="comment">
|
|
|
|
<table width="100%">
|
|
|
|
<tbody>
|
|
<tr>
|
|
|
|
<td rowspan="2">
|
|
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#p20140731">p20140731</a>
|
|
<br>
|
|
Editor: Iang 20080309
|
|
<br>
|
|
Changes: 20100507, 20130223, 20140731
|
|
<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>
|
|
<br>
|
|
</td>
|
|
|
|
<td align="right" valign="top">
|
|
<a href="https://www.cacert.org/policy/PolicyOnPolicy.php">
|
|
<img src="images/cacert-policy.png" alt="PoP Status - POLICY" style="border-style: none;" height="31" width="88">
|
|
</a>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
|
|
<p>
|
|
<br>
|
|
</p>
|
|
|
|
<h1> Policy on Policy </h1>
|
|
|
|
|
|
|
|
<h2 id="g0.1">0. Preliminaries </h2>
|
|
<p>
|
|
Policy on Policy adopts the IETF model of
|
|
'rough consensus' to create CAcert documents
|
|
within the open CAcert Policy Group <a href="https://lists.cacert.org/wws/info/cacert-policy"> mail list forum</a>.
|
|
</p>
|
|
|
|
|
|
<h2 id="g0.2">1. Scope and Purpose </h2>
|
|
|
|
<p id="s1.1">
|
|
1.1
|
|
This policy documents and controls the process by which
|
|
CAcert creates and promulgates policies.
|
|
</p>
|
|
|
|
<p id="s1.2">
|
|
1.2
|
|
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.
|
|
</p>
|
|
|
|
<p id="s1.3">
|
|
1.3
|
|
The policies so created are generally binding on
|
|
CAcert Inc., members under CAcert Community Agreement
|
|
(CCA => COD9) and other related parties under other agreements.
|
|
</p>
|
|
|
|
<p id="s1.4">
|
|
1.4
|
|
The Policy Officer manages all policies
|
|
and the policy group.
|
|
The policy group is formed on the open mailing list
|
|
known as CAcert Policy Group, and is to be open to all
|
|
Community Members of CAcert.
|
|
</p>
|
|
|
|
|
|
<h2 id="g0.3">2. Basic Model </h2>
|
|
|
|
<p id="s2.1">
|
|
2.1
|
|
The basic concept was drawn from the IETF model.
|
|
</p>
|
|
|
|
<p id="s2.2">
|
|
2.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>
|
|
|
|
<p id="s2.3">
|
|
2.3
|
|
Decisions are taken by "Rough Consensus."
|
|
A vote may be called to clarify.
|
|
</p>
|
|
|
|
<p id="s2.4">
|
|
2.4
|
|
Documents should include a minimum of information
|
|
in a standardised format managed by the Documentation Officer:
|
|
the Title,
|
|
short name,
|
|
Document Status,
|
|
date the Status was reached,
|
|
Editor,
|
|
date / time of the last edit,
|
|
Abstract.
|
|
</p>
|
|
|
|
<p id="s2.5">
|
|
2.5
|
|
Editors may make the following changes, where
|
|
it is clear that the change does not change the policy:</p>
|
|
<ul>
|
|
<li>
|
|
fixes to errors in grammar and spelling,
|
|
</li>
|
|
<li>
|
|
anchors, HTML errors, URLs & formatting,
|
|
</li>
|
|
<li>
|
|
COD numbers and other references, and
|
|
</li>
|
|
<li>
|
|
other minutiae, as agreed under 2.3.
|
|
</li>
|
|
</ul>
|
|
<p>
|
|
Such changes to be notified to the policy group, and to be folded into effect, etc, without further ado.
|
|
</p>
|
|
|
|
|
|
<p id="s2.6">
|
|
2.6
|
|
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 id="g0.4">3. Work-In-Progress </h2>
|
|
|
|
<p id="s3.1">
|
|
3.1
|
|
An Editor is identified.
|
|
This person is responsible for
|
|
drafting the document, following the consensus of the policy group.
|
|
</p>
|
|
|
|
<p id="s3.2">
|
|
3.2
|
|
The Policy Officer resolves minor disputes and keeps order.
|
|
</p>
|
|
|
|
<p id="s3.3">
|
|
3.3
|
|
The mail list of the policy group
|
|
is used as the primary debating
|
|
forum. A sub-group may be formed,
|
|
but decision-taking
|
|
should be visible on the main group.
|
|
</p>
|
|
|
|
<p id="s3.4">
|
|
3.4
|
|
Documents start with the status of
|
|
"Work-In-Progress" or WIP for short.
|
|
</p>
|
|
|
|
|
|
<h2 id="g0.5">4. DRAFT status </h2>
|
|
|
|
<p id="s4.1">
|
|
4.1
|
|
On completion, a document moves to DRAFT status.
|
|
</p>
|
|
|
|
<p id="s4.2">
|
|
4.2
|
|
A DRAFT is a policy-in-effect for the Community and is
|
|
to be distributed and treated as such.
|
|
</p>
|
|
|
|
<p id="s4.3">
|
|
4.3
|
|
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.
|
|
</p>
|
|
|
|
<p id="s4.4">
|
|
4.4
|
|
Revisions of DRAFTs
|
|
must be treated as decisions on the policy group.
|
|
</p>
|
|
|
|
<p id="s4.5">
|
|
4.5
|
|
The period of the DRAFT status is announced widely,
|
|
which should be at least a month and no longer than a year.
|
|
</p>
|
|
|
|
<p id="s4.6">
|
|
4.6
|
|
During the period of DRAFT,
|
|
CAcert Inc. retains a veto over
|
|
policies that effect the running of CAcert Inc.
|
|
</p>
|
|
|
|
<h2 id="g0.6">5. POLICY status </h2>
|
|
<p id="s5.1">
|
|
5.1
|
|
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.
|
|
</p>
|
|
|
|
<p id="s5.2">
|
|
5.2
|
|
Once POLICY, the Community may only challenge the document
|
|
in Dispute Resolution.
|
|
</p>
|
|
|
|
<p id="s5.3">
|
|
5.3
|
|
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.
|
|
</p>
|
|
|
|
<p id="s5.4">
|
|
5.4
|
|
POLICY documents are published on the CAcert website in plain HTML. Change control must be in place.
|
|
</p>
|
|
|
|
<h2 id="g0.7">6. Open Process </h2>
|
|
|
|
<p id="s6.1">
|
|
6.1
|
|
All policy discussions and documents should be open
|
|
processes. There should be a fair chance for
|
|
the Community
|
|
to have their views heard.
|
|
Rough Consensus is the working metric.
|
|
</p>
|
|
|
|
<p id="s6.2">
|
|
6.2
|
|
Contributions to
|
|
formally controlled documents such as Policies
|
|
are transferred fully to CAcert Inc.
|
|
Copyrights
|
|
and similar intellectual property rights
|
|
required to incorporate the Contribution
|
|
are either transferred to CAcert Inc, or,
|
|
are issued and contributed under free,
|
|
open, non-restrictive,
|
|
irrevocable, exclusive,
|
|
and clear licence to CAcert Inc.
|
|
In all cases, CAcert Inc licenses the
|
|
contributions back to the community
|
|
under an open licence.
|
|
</p>
|
|
|
|
<p id="s6.3">
|
|
6.3
|
|
Contributors declare any conflicts of interest.
|
|
</p>
|
|
|
|
<p id="s6.4">
|
|
6.4
|
|
Policies should be issued under free, open,
|
|
non-restrictive,
|
|
irrevocable, non-exclusive,
|
|
and clear licence by CAcert, Inc.
|
|
</p>
|
|
|
|
<p id="s6.5">
|
|
6.5
|
|
Mailing lists should be archived,
|
|
and important meetings should be minuted.
|
|
A record of decisions is to be maintained.
|
|
</p>
|
|
|
|
<h2 id="g0.8">7. Disputes. </h2>
|
|
|
|
<p id="s7.1">
|
|
7.1
|
|
Any questions not resolved by these rules
|
|
may be voted on in the policy group, or
|
|
may be dealt with in Dispute Resolution.
|
|
</p>
|
|
|
|
<p id="s7.2">
|
|
7.2
|
|
The Policy Officer may decide a tight vote in a minor matter only.
|
|
Failure of Rough Consensus may be declared by
|
|
dissenting members.
|
|
</p>
|
|
|
|
<p id="s7.3">
|
|
7.3
|
|
Matters unresolved refer back
|
|
to further group discussion.
|
|
</p>
|
|
|
|
<p id="s7.4">
|
|
7.4
|
|
The external avenue for disputes is to file a dispute
|
|
according to CAcert's
|
|
<a href="https://www.cacert.org/policy/DisputeResolutionPolicy.php">
|
|
Dispute Resolution Policy</a>
|
|
DRP => COD7.
|
|
</p>
|
|
|
|
|
|
</body>
|
|
</html>
|