Policy-Discussion

[Andreas Bürki <abuerki AT cacert.org>]

Ian G schrieb:
> 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


In my humble opinion: Keep SP in Draft for an other period of one year
from the last change, the blue one's

We need to know, how this works in practice. Arguing for other solutions
does not replace practical experience and potential, practical consequences.


cheeeerio, hugi



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


-- 
Andreas Bürki - 
abuerki AT cacert.org
CAcert Assurer for People & Organizations

CAcert.org - Secure Together
http://www.cacert.org