RFC security-process: update with mailing list details
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest1 patch 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | security-process: update process informationcontribute/ | +55 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/1] security-process: update with mailing list details
From: Prasad J Pandit <[email protected]>
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 <[email protected]> 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