We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the Usage Guidelines given to open source developers on the README in this repo we have the following statement
| Code being run must be 100 percent open source and must not include any sensitive data.
(emphasis added)
We have been asked to provide a definition of sensitive data by @LucaGuerra from the Falco Project
As the question raised is not project-specific and relevant to the entire community I'm raising the issue here.
The two obvious areas to consider wrt to sensitive data are
@jeefy PTAL and let us know how we would like to define sensitive data for the applicants
cc @caniszczyk @amye @krook
The text was updated successfully, but these errors were encountered:
FYI @lukaszgryglicki I reviewed
https://github.com/cncf/cluster/blob/b80b8a9b953c3ad3a65b0276970bf73b547eaa10/TERMS_OF_USE.md
It is a useful document wrt defining prohibited and unacceptable uses of the resources in the lab.
Sorry, something went wrong.
RobertKielty
jeefy
No branches or pull requests
In the Usage Guidelines given to open source developers on the README in this repo we have the following statement
| Code being run must be 100 percent open source and must not include any sensitive data.
(emphasis added)
We have been asked to provide a definition of sensitive data by @LucaGuerra from the Falco Project
As the question raised is not project-specific and relevant to the entire community I'm raising the issue here.
The two obvious areas to consider wrt to sensitive data are
@jeefy PTAL and let us know how we would like to define sensitive data for the applicants
cc @caniszczyk @amye @krook
The text was updated successfully, but these errors were encountered: