-
Notifications
You must be signed in to change notification settings - Fork 22
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
Prepare all Repos to go PUBLIC #98
Comments
Additionally, we need to have some Security Guidelines document. We could use this one here: https://github.com/SAP/.github/blob/main/SECURITY.md We will have to copy and paste the content, as parts don't make sense for us, as we have our own organization and therefore are not part of the SAP org. |
Great! We can definitely add this. Previously we were given the Gardener Security Release Process as a reference for the Security Policy. I wanted to raise this with you because it was quite specific and hard to apply to OCM. However, this Security Policy that you have linked to looks applicable. I will add it. :) |
Here is the Flux Security policy: https://github.com/fluxcd/.github/blob/main/SECURITY.md |
During the last planning meeting, we decided to pause the Security Policy as it is not a blocker to going live. It is still a requirement. Here is a separate ticket added to the backlog: #153 |
Closing as the three tasks mentioned in the description are done. |
Description
All Repositories under "open-component-model" have to adhere to certain standards before we can switch them from
private
topublic
. These standards include:The text was updated successfully, but these errors were encountered: