Policy-Discussion

[<ulrich AT cacert.org>]

I vote for #1

thus doesn't mean, that we cannot vote SP for Policy
in i.e. one month as the blue sections are discussed
and have been fixed.

from my PoV the blue additions are an essential part,
but currently the process of transfer packages
from the main repository to the critical
system under development, so there is no procedure
yet fixed.

Here there is some rework to do until the procedures
are written


regards, uli   ;-)


-----Original Message-----
From: Ian G 
[mailto:iang AT cacert.org]
Sent: Monday, March 22, 2010 10:14 PM
To: Policy-Discussion
Subject: SP => POLICY?


According to PoP, a policy can only be in DRAFT for a year ...

Security Policy reaches this milestone this Saturday, following p20090327.

https://svn.cacert.org/CAcert/Policies/SecurityPolicy.html

Now, there are some marked up suggestions in BLUE that have not been
voted upon.  These basically add an "Application Engineer" who is
responsible for the application.  We would need to make a bit of a
decision here as to which way we want to go.

1.  Keep SP in DRAFT for another period, and
     re-work those BLUE sections.

2.  Accept the BLUE, and go to POLICY.

3.  Discard the BLUE as not voted, and go to POLICY.

4.  Or?



What do policy group people vote for?



iang

PS: Green should disappear.

Attachment: smime.p7s
Description: S/MIME cryptographic signature