From 32b9588463ab4f94489ec8dd44b6b90215811cd7 Mon Sep 17 00:00:00 2001 From: Ian Grigg Date: Mon, 25 Feb 2008 13:29:01 +0000 Subject: [PATCH] Some minor changes to bring it into line with later decisions: COD number is now 3. Name should have Policy at end. git-svn-id: http://svn.cacert.org/CAcert/Policies@610 14b1bab8-4ef6-0310-b690-991c95c89dfd --- DocumentsPolicy.html | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/DocumentsPolicy.html b/DocumentsPolicy.html index 61ac081..eede73b 100644 --- a/DocumentsPolicy.html +++ b/DocumentsPolicy.html @@ -1,13 +1,15 @@ -COD 1 : Policy on Documents - - - + +COD3 : CAcert Official Documents Policy - + - -

Policy on Documents

+ + + +
W o r k -- i n -- P r o g r e s s
+ +

CAcert Official Documents Policy

Table of Contents

0. General
0.1. Document Information
@@ -38,8 +40,8 @@

0. General

0.1. Document Information

-Document-ID: COD 1-V1-DRAFT
-Status: Draft
+Document-ID: COD3
+Status: wip V0.2
(C): 2007 Sebastian Kueppers

0.2. References

@@ -53,7 +55,7 @@ This document provides information for authors of CAcert Official Documents (COD be supervised and versionized for legal (e.g. policies) or handy (e.g. the document how to organize events) reasons.
Policies and other documents that are covered by the Configuration -Control Specification (-> COD 2) contain a corresponding note in +Control Specification (-> COD2) contain a corresponding note in their "general" section (see below).
It summarizes COD editorial policies and formatting requirements, answers frequently asked questions, and serves as a model for @@ -177,7 +179,7 @@ of references. If a table of contents is available this section is usually lablled as section "0".
If a COD is a policy of CAcert Inc and/or controlled by the "Configuration Control SpecificationConfiguration Control -Specification" (-> COD 2) this fact is stated in this section, too. +Specification" (-> COD2) this fact is stated in this section, too.

3.4. Body section

The general section is followed by the document body.
Each COD should have an introduction that explains the motivation for the @@ -203,6 +205,6 @@ to the document any more. Author: Sebastian Kueppers, cacert@kueppers.ath.cx

-<-- END OF COD 1 --> +<-- END OF COD3 --> - \ No newline at end of file +