[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Formal Vote for changes to Xen Project Security Policy encoded in [PATCH v2 SECURITY-POLICY */9] (vote ends next Wed, Feb 11th)

Hi all,

seems we have for in favour and no objections. So the change carries.

@Ian Jackson: 
I suppose we need to get the list(s) created that were referenced, sign up core 
members, before we can go fully life with this change. Also, please send me the 
complete text such that I can upload it. I have not added any new vendors, such 
that there are no merge conflicts. I think there may have been one or two that 
need to be added as part of the old policy.


> On 3 Feb 2015, at 12:09, Lars Kurth <lars.kurth.xen@xxxxxxxxx> wrote:
> Hi all,
> the patch series for modifications to 
> http://www.xenproject.org/security-policy.html has gone it's second revision 
> and is ready for voting. In accordance with our governance, committers are 
> eligible to vote. Others can of course voice their opinion.
> The complete series can be found in the following mails
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03021.html - [PATCH 
> v2 SECURITY-POLICY 0/9] Security policy ambiguities - XSA-108 process 
> post-mortem
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03020.html - [PATCH 
> v2 SECURITY-POLICY 1/9] Grammar fix: Remove a comma splice
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03018.html - [PATCH 
> v2 SECURITY-POLICY 2/9] Add headings
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03016.html - [PATCH 
> v2 SECURITY-POLICY 3/9] Deployment with Security Team Permission
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03022.html - [PATCH 
> v2 SECURITY-POLICY 4/9] Use a public mailing list for predisclosure 
> membership applications.
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03019.html - [PATCH 
> v2 SECURITY-POLICY 5/9] Tighten, and make more objective, predisclosure list 
> application
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03015.html - [PATCH 
> v2 SECURITY-POLICY 6/9] Explicitly permit within-list information sharing 
> during embargo
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03014.html - [PATCH 
> v2 SECURITY-POLICY 7/9] Clarify and fix prior consultation text
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03017.html - [PATCH 
> v2 SECURITY-POLICY 8/9] Clarify what announcements may be made by to service 
> users
> * http://lists.xen.org/archives/html/xen-devel/2015-01/msg03023.html - [PATCH 
> v2 SECURITY-POLICY 9/9] Document changes in changelog and heading
> As there seems to be no objections, in the discussion leading to this patch 
> series, I think we don't need to have a voting form. Replying to this mail 
> with +1, 0 -1 "comment" should suffice. Should there be objections and they 
> are specific to a specific change above, please refer to the specific change.
> I will collate the results on Thursday and make an announcement
> All committers are CC'ed
> Regards
> Lars

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.