From: P J P <ppandit@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: peter.maydell@linaro.org,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Petr Matousek" <pmatouse@redhat.com>,
"Prasad J Pandit" <pjp@fedoraproject.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
secalert@redhat.com, "Michael Roth" <michael.roth@amd.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Darren Kenny" <darren.kenny@oracle.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: [RFC 0/1] security-process: update with mailing list details
Date: Tue, 24 Nov 2020 19:52:37 +0530 [thread overview]
Message-ID: <20201124142238.225417-1-ppandit@redhat.com> (raw)
From: Prasad J Pandit <pjp@fedoraproject.org>
Hello,
* After upstream discussions and considering various options like
LaunchPad bugs, GitLab issues etc.
-> https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg04266.html
-> https://lists.nongnu.org/archive/html/qemu-devel/2020-10/msg00059.html
We are about to introduce a 'qemu-security' mailing list to receive and
triage upstream QEMU security issues.
* Intention is to allow more community participation in handling and
triaging of the QEMU security issues.
* This change relieves current set of individual contacts from the
responsibility of handling upstream QEMU issues. Of course they are
welcome to the new 'qemu-security' mailing list.
* To simplify the encrypted communication process, we keep only a single
contact of <secalert@redhat.com> from our previous list of contacts.
This way reporters need not look for and manage GPG keys of multiple
contacts.
* This patch updates the QEMU security-process web page with these
details.
I'd appreciate if you have any inputs and/or suggestions for this change.
Thank you.
--
Prasad J Pandit (1):
security-process: update process information
contribute/security-process.md | 105 +++++++++++++++++----------------
1 file changed, 55 insertions(+), 50 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-24 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 14:22 P J P [this message]
2020-11-24 14:22 ` [RFC 1/1] security-process: update process information P J P
2020-11-24 16:23 ` Darren Kenny
2020-11-25 12:48 ` P J P
2020-11-25 14:44 ` Darren Kenny
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=20201124142238.225417-1-ppandit@redhat.com \
--to=ppandit@redhat.com \
--cc=berrange@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pjp@fedoraproject.org \
--cc=pmatouse@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=secalert@redhat.com \
--cc=sstabellini@kernel.org \
--cc=stefanha@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).