Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SECURITY.md #264

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add SECURITY.md #264

wants to merge 1 commit into from

Conversation

AlexanderBand
Copy link
Member

No description provided.

@AlexanderBand AlexanderBand added this to the 0.10.0 milestone Feb 5, 2024
@AlexanderBand AlexanderBand requested a review from a team February 5, 2024 10:50
@AlexanderBand AlexanderBand removed this from the 0.10.0 milestone Feb 5, 2024
@partim partim marked this pull request as draft February 5, 2024 11:22
Copy link
Member

@maertsen maertsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two general observations:

  • the term 'support' is not defined here, nor on our website. The filename and first heading here implicitly conveys that 'support' is related to 'security', while the (same) text on the website is not in a security specific context and presumably is about where continued development happens.
  • the (general) statement about no backporting of security fixes may be read to conflict with the (specific) statement about support for the latest minor version of a previous major version. I am assuming that "specific beats general" and therefore this is an exception to the 'no backporting' rule. But perhaps it is not. I think it would be helpful to clarify this.


## Reporting a Vulnerability

We take security very seriously. If you have discovered a security vulnerability
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We take security very seriously. If you have discovered a security vulnerability
If you have discovered a security vulnerability

## Reporting a Vulnerability

We take security very seriously. If you have discovered a security vulnerability
in one of our projects and you would like to report it to us, you can send an
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
in one of our projects and you would like to report it to us, you can send an
in one of our projects and you would like to report it to us, please send an

older (minor) versions. In the event a new major version is released (e.g. from
3.2.18 to 4.0.0), support will also be provided on the latest minor version of
the previous major version (3.2.18) for a period of one year from the release of
the new major version (4.0.0).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
the new major version (4.0.0).
the new major version (4.0.0), unless the previous major version number was 0 (the 'initial development phase').

@AlexanderBand AlexanderBand marked this pull request as ready for review February 27, 2024 09:52
@partim
Copy link
Member

partim commented Feb 27, 2024

I also stumbled over the lack of definition of “support.” I’m assuming it to mean security and bug fixes, but we should probably say that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants