Skip to Content.
Sympa Menu

cacert-policy - Re: SP => POLICY?

Subject: Policy-Discussion

List archive

Re: SP => POLICY?


Chronological Thread 
  • From: Lambert Hofstra <lamberthofstra AT gmail.com>
  • To: cacert-policy AT lists.cacert.org
  • Subject: Re: SP => POLICY?
  • Date: Sat, 27 Mar 2010 22:52:59 +0100
  • Authentication-results: lists.cacert.org; dkim=pass (1024-bit key) header.i= AT gmail.com; dkim-asp=none
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=ksOK8GtfrNXXuzeENCTGtL9flEgxUwZMEk2cPy9dzInSShqqwdBmVSbzFBjVuLyBUn T/5z5k9xXR5ekisNP2J7rjtQHV4YNtSBC8h7CgO5W67XFvj8daacP5xwfyM2a0Yy2lUu RMZ3uV9y5Tk6NoHKztUojt1+PkzGXsIW74u6g=

I'm in favour of option 1

Lambert


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




Archive powered by MHonArc 2.6.16.

Top of Page