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>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Darren Kenny" <darren.kenny@oracle.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: [PATCH v2 0/1] security-process: update with mailing list details
Date: Thu, 3 Dec 2020 19:59:01 +0530 [thread overview]
Message-ID: <20201203142902.474883-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.
v1:
* This patch v1 updates the QEMU security-process web page with detailed
process.
-> https://lists.nongnu.org/archive/html/qemu-devel/2020-11/msg06234.html
v2:
* Incorporate further inputs and suggestions from upstream reviews.
-> https://lists.nongnu.org/archive/html/qemu-devel/2020-12/msg00568.html
-> https://lists.nongnu.org/archive/html/qemu-devel/2020-12/msg00584.html
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 | 154 ++++++++++++++++++++-------------
1 file changed, 95 insertions(+), 59 deletions(-)
--
2.28.0
next reply other threads:[~2020-12-03 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 14:29 P J P [this message]
2020-12-03 14:29 ` [PATCH v2 1/1] security-process: update process information P J P
2020-12-03 14:38 ` Daniel P. Berrangé
2020-12-03 15:43 ` Darren Kenny
2020-12-10 14:17 ` Petr Matousek
2020-12-10 17:36 ` Michael Roth
2020-12-10 21:14 ` Stefano Stabellini
2020-12-10 21:39 ` Konrad Rzeszutek Wilk
2021-01-14 15:26 ` Philippe Mathieu-Daudé
2021-01-14 15:31 ` P J P
2021-01-14 15:32 ` Philippe Mathieu-Daudé
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=20201203142902.474883-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=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).