Skip to Content.
Sympa Menu

cacert-policy - Re: SP => POLICY?

Subject: Policy-Discussion

List archive

Re: SP => POLICY?


Chronological Thread 
  • From: Daniel Black <daniel AT cacert.org>
  • To: cacert-policy AT lists.cacert.org
  • Subject: Re: SP => POLICY?
  • Date: Thu, 25 Mar 2010 13:15:40 +1100
  • Authentication-results: lists.cacert.org; dkim=pass (1024-bit key) header.i= AT cacert.org; dkim-asp=none
  • Organization: CAcert

On Tuesday 23 March 2010 08:13:58 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.

my preference is this mainly because of the other issues raised in previous 
email by me.

> 2.  Accept the BLUE, and go to POLICY.

I'm happy to accept the all Application Engineer changes. I think the board 
could quickly appoint all Sysadmins to the Application Engineer category to 
provide continuity and not incur an immediate increase in Sysadmin work.

-- 
Daniel Black
CAcert

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




Archive powered by MHonArc 2.6.16.

Top of Page