Skip to content
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

Licensing the docker-rust repository #206

Open
Kobzol opened this issue Jul 17, 2024 · 2 comments
Open

Licensing the docker-rust repository #206

Kobzol opened this issue Jul 17, 2024 · 2 comments

Comments

@Kobzol
Copy link
Contributor

Kobzol commented Jul 17, 2024

Me and @Muscraft would like to add a license to this repository. Multiple people have asked for this (#12, rust-lang/docker-rust-nightly#14), and it is a good idea overall. The effort should be quite similar to the recent licensing of rustc-perf.

I think that we can use our default Rust Project license, i.e. a combined MIT/Apache-2.0 license. As usually, we will need to contact contributors that have contributed code to this repository previously, to get their permission. Furthermore, since this repository contains code from https://github.com/rust-lang/docker-rust-nightly (which has been since archived), we should also ask people who contributed to that repository for their approval. I ran my script on these two repositories, it should be 21 people in total.

I would propose the following approach:

  1. Create a PR that adds a license, so that people can check the license wording (there is already Adding License Statement (MIT and Apache) #74, but I'm not sure if @TimmFitschen is still around, if not, we can create a new one).
  2. Create a new issue, like this one, where we will ask contributors for their approval, with the following text:
I license my past contributions to the `rust-lang/docker-rust` and `rust-lang/docker-rust-nightly` repositories under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
  1. Wait until we get the approval of contributors, and then merge the PR with the new license.

@abibroom Any thoughts/concerns?

@abibroom
Copy link

Sounds good to me!

@TimmFitschen
Copy link

I updated #74 . Please use it if you like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants