From: Lars Kurth <lars.kurth@xen.org>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"xen-users@lists.xen.org" <xen-users@lists.xen.org>
Subject: [Final Community Review] Xen Security Problem Response Process v2
Date: Fri, 10 May 2013 17:11:49 +0100 [thread overview]
Message-ID: <518D1C45.5070601@xen.org> (raw)
Dear Community Members,
In the last update about the security problem response process changes
(http://blog.xen.org/index.php/2012/12/17/security-disclosure-process-discussion-update),
we promised a vote in mid-January. Near the end of the window, some
additional changes were proposed, and we were somewhat sidetracked with
launching Xen as a Linux Foundation Collaborative Project.
As this process impacts many Xen users, we feel that it is prudent to
run through a final week of community review (closing on Monday May 20th).
The proposal can be found at
http://www.xenproject.org/component/content/article/85-about-xen/138-xen-security-problem-response-process-v2-proposal.html
Significant changes to the document are:
- Expand eligibility of who can join the predisclosure list
- Clarify definitions of who can join the predisclosure list
- Clarify information that needs to be supplied when joining the
predisclosure list
- Change e-mail alias to security@xenproject
Review comments are to be posted in response to this thread (on
xen-devel and xen-users). Please do not revisit arguments, which have
been made at length in previous discussions. Hopefully, we got this
right now and can move forward with a formal vote in the last week of
May and get the new process implemented.
Best Regards
Lars
reply other threads:[~2013-05-10 16:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=518D1C45.5070601@xen.org \
--to=lars.kurth@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.