Policy-Discussion

[Nathan Edward Tuggy <nathantuggy AT sti.net>]

I must admit that initially I favored option 2, but after re-reading the 
draft, I think it probably does need at least a little bit more 
polishing. So I'll cast my vote in favor of keeping in draft (#1), 
albeit for as little time as possible.

On 2010-03-22 14:13, Ian G wrote:
> 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.

--
Nathan E Tuggy
Software Professional, Security Enthusiast, CAcert Member

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature