Create SECURITY.md#749
Merged
Merged
Conversation
tomkralidis
requested review from
GeoSander,
alpha-beta-soup,
francbartoli,
jorgejesus,
justb4,
kalxas and
pvgenuchten
August 3, 2021 20:15
francbartoli
requested changes
Aug 4, 2021
francbartoli
approved these changes
Aug 10, 2021
Merged
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.
FYI, per https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository. Thanks to @jmckenna for the inspiration.
Interested in folks' feedback here about the contact point. I put myself only because we don't have a dedicated security/private email address. Should we? Or is this too much overhead? I also thought of using OSGeo's security-priv, but non-members won't be able to send email. I would also prefer someone else as the contact (or at least two PSC members).