Add a CVE Triage Checklist to the rules#40
Open
todb wants to merge 3 commits into
Open
Conversation
First draft of a triage guide in the rules
Collaborator
|
SPWG briefly discussed this today, in general terms of "companion documentation." Rough consensus in SPWG is that this is useful but should live separately from the official Rules document. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello, CVE! Please see this proposed update to the rules! It actually doesn't change or add or remove any rules, but instead, offers a cheat sheet for CNAs to answer basic questions of "should I write a CVE for this bug?"
We think it would be useful to incorporate this into the rules directly. I'll follow this up with a note to the CVE Board for discussion.