-
Notifications
You must be signed in to change notification settings - Fork 1
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
Which license to use? #1
Comments
I think since the images themselves are hosted by Github Package Registry, maybe the license problems don't apply to us? In that case Apache 2.0 would suffice, which by coincidence is also used by the simdjson library and the official docker repository! |
Surely, we are not the first project to look at packaging their own images for CI purposes. Have you encountered other sizeable projects that do so? How do they handle the licensing of their custom images? |
Unfortunately, I have not yet come across such a project. |
We'll have to find someone who can provide advice then. I do not know. |
I think that publishing the docker scripts is fine for sure (I do so all the time), but the images are something else. They carry binary code and so forth. |
I think it is probably safe to look at docker-library/official-images for what would be appropriate for a repository with just
Dockerfile
s.However, I found this page describing some points to look out for. The accepted answer is pretty detailed and seems to address my concerns.
cc: @lemire
The text was updated successfully, but these errors were encountered: