From a47ed49998032fbb22de5f48c6ecfc44dc9ef34e Mon Sep 17 00:00:00 2001 From: Ian Grigg Date: Fri, 7 May 2010 14:54:15 +0000 Subject: [PATCH] a set of suggested changes taken from CCS work git-svn-id: http://svn.cacert.org/CAcert/Policies@1896 14b1bab8-4ef6-0310-b690-991c95c89dfd --- PolicyOnPolicy.html | 92 +++++++++++++++++++++++++++++++++++++++------ 1 file changed, 81 insertions(+), 11 deletions(-) diff --git a/PolicyOnPolicy.html b/PolicyOnPolicy.html index 7992528..d11dd3e 100644 --- a/PolicyOnPolicy.html +++ b/PolicyOnPolicy.html @@ -1,8 +1,58 @@ - - - -Policy on Policy - + + + + + + Policy on Policy + + + + +

+

+ +
WARNING:
+ The proper policy document is located
+ + on the CAcert website .
+ + This document is a working draft to include
+ future revisions only, and is currently
+ only relevant for the [policy] group.
+ Suggested additions in BLUE, strikes in blue.
+
+ Iang 20100507: fixed two errors being cacert-policy and 1.3 terminology.
+ Iang 20100507: incorporated suggestions from CCS - 2.3, 5.4, 6.5
+

+
@@ -13,10 +63,10 @@ - + @@ -39,7 +89,7 @@

Policy on Policy adopts the IETF model of 'rough consensus' to create CAcert documents - within the open [policy] mail list forum. + within the open [cacert-policy] mail list forum.

@@ -64,7 +114,9 @@ and also documents part of the CCS.

1.3 The policies so created are generally binding on -CAcert, registered users and related parties. +CAcert, registered users and related parties +CAcert Inc., members under CAcert Community Agreement +(CCA => COD9) and other related parties under other agreements.

@@ -72,7 +124,7 @@ CAcert, registered users and related parties. 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 [cacert-policy], and is to be open to all Community Members of CAcert.

@@ -109,6 +161,14 @@ date / time of the last edit, Abstract.

+

+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. +

+

3. Work-In-Progress

@@ -204,6 +264,15 @@ they may be included in the POLICY document, but must be clearly indicated within as DRAFT not POLICY.

+

+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 +Security Policy +SP => COD8. +

+

6. Open Process

@@ -250,6 +319,7 @@ and clear licence by CAcert, Inc. 6.5 Mailing lists should be archived, and important meetings should be minuted. +Policy Officer is to maintain a record of decisions.

7. Disputes.

@@ -278,7 +348,7 @@ to further group discussion. 7.4 The external avenue for disputes is to file a dispute according to CAcert's - + Dispute Resolution Policy DRP => COD7.

POLICY p200800204.1 POLICY p200800204.1 - 20080309 + 20080309, 20100507