-
Notifications
You must be signed in to change notification settings - Fork 89
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
Tooling and processes to ensure licensing requirements for Docker images are satisfied #539
Labels
Comments
Made PR for tools for automating go dependencies' licenses: #540 |
@zhenghuiwang could you provide an update on this? |
This was referenced Dec 16, 2019
Update: Filed several issues above. For Golang image: follow these instructions to add license files. For NodeJS image: follow these instructions to add license files. |
zhenghuiwang
added a commit
to kubeflow/community
that referenced
this issue
Jan 3, 2020
k8s-ci-robot
pushed a commit
to kubeflow/community
that referenced
this issue
Jan 3, 2020
@zhenghuiwang can we close this issue or is there more work to be done? |
Merged
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need tooling and processes to ensure that all the docker images we publish satisfy appropriate licensing requirements.
This is critical for 1.0
To begin with I think we can focus on docker images for applications going 1.0 with Kubeflow 1.0. I think we basically have two kinds of docker images
For each of these binaries we need to transitively pull all third party dependencies and ensure we satisfy licensing requirements.
The text was updated successfully, but these errors were encountered: