-
Notifications
You must be signed in to change notification settings - Fork 385
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
Mention about the Embargo Policy for the licensing subproject #636
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We require folks to follow the Embargo Policy if they have access to any security issues. Both members of the Product Security Committee and GitHub mananagement team are subject to this policy.
I just realized that it might be useful to codify that members (owners?) of the licensing subproject are also subject to this policy, especially if they come across any serious concerns or have access to FOSSA.
@swinslow Can you confirm if this would make sense from a legal perspective or would this be unnecessary?
/cc @justaugustus @dims
/area licensing
/assign @swinslow
to confirm if this is needed
/assign
if needed, I'll add it in the docs
The text was updated successfully, but these errors were encountered: