[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Security policy ambiguities - XSA-108 process post-mortem
>>> On 21.10.14 at 16:31, <msw@xxxxxxxxx> wrote: > On this point in particular, back in 2012 [1] I suggested that all > membership requests should be discussed in public on a community email > list like xen-devel, or another email list to avoid noise. The Xen > Project Security Team shouldn't have to evaluate petitions for > membership while managing an embargoed issue. I brought this up again > in 2013 [2] regarding the Coverity process. And indeed I had intended to bring this point up too, but then forgot. So - thanks for raising this! Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |