-
Notifications
You must be signed in to change notification settings - Fork 243
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
Proposal for establishing the SIG Security #1333
Comments
@reyang volunteered to be a sponsor for this proposal. |
Yup 👍 |
thanks for the trust and +1 |
+1 on this initiative! It would be great if the security of our Github actions/workflows/automations/secrets and repo settings could be covered there as well. |
definitely we can work on those things as well |
@jpkrohling consider borrow from open-telemetry/opentelemetry-specification#3112 PR description. |
I had too many things on my plate and couldn't follow up. I'll likely be able to give more attention to this and make a formal proposal for this SIG following @reyang's suggestion. |
I'm willing to help out @jpkrohling |
I created a draft issue @cpanato @jpkrohling |
SIG is there for a while now, closing. |
Based on the discussion from open-telemetry/opentelemetry-collector-releases#207, I would like to propose the creation of the SIG Security. The SIG would be responsible for establishing the patterns to be adopted by other SIGs and repositories, as well as serve as a go-to place for security inquiries.
Initially, the SIG would have @cpanato and me, and we are open to having anyone else who'd want to join us.
This would NOT be a security response team (although we can kick off a discussion around that if needed).
The text was updated successfully, but these errors were encountered: