-
Notifications
You must be signed in to change notification settings - Fork 231
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
REQUEST: Create new team open-telemetry/semconv-security-approvers #2100
Comments
(cc @open-telemetry/specs-semconv-maintainers) |
nit: could you please change the suggested name to plural |
@trisch-me I created the group @open-telemetry/semconv-security-approvers and added it to our semconv repo. You can go ahead and adjust the CODEOWNERS file already. I was able to add you @trisch-me and @alexvanboxel to the team right away. For the new faces, they'll need to become a member of the Github organization first by following the process defined at https://github.com/open-telemetry/community/blob/main/community-membership.md#member once they fulfill the requirements listed there and then we can add them as well. @jsuereth and @reyang I also added you as the TC sponsors as per https://github.com/open-telemetry/community/blob/main/projects/security-semconv.md#required-staffing. |
Thank you @arminru |
Thanks @arminru ! |
@arminru Can you add me to this group; I'm now in the OpenTelemetry org |
I would like to create a group @open-telemetry/semconv-security-approvers for all PRs related to security fields in following namespaces (some of them are not present now(*) but will be added soon):
process
tls
dll*
dns*
file
registry*
user
vulnerability*
x509 Certificate*
threat*
and more namespaces to come into security field
Members of the group:
Project: https://github.com/open-telemetry/community/blob/main/projects/security-semconv.md
The text was updated successfully, but these errors were encountered: