Open Muscraft opened 3 months ago
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
I license my 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.
:clinking_glasses:
I license my 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.
I license my 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.
I license my 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.
@rminami, we are currently in the process of relicensing docker-rust
(read here for details), and since you contributed after this issue was created, you weren't in the original list of users. Since that is the case, I figured it would be better to comment to let you know about it.
@rminami Could you please take a look? Thanks!
I license my 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.
This repository currently does not have a LICENSE file (https://github.com/rust-lang/docker-rust/issues/12). We would like to license the code in this repository under the dual MIT/Apache-2.0 license, which is a standard dual license used for Rust Project repositories.
To do that, we need contributors that made commits to this repository (and also to the docker-rust-nightly repository, since some of its code is reused in this repo) to agree by posting a comment stating their approval to this issue. Please see instructions at the bottom of this issue if you are mentioned in the list below. We will try to also contact the contributors individually.
How did we select the list of contributors from whom we need the approval?
We analyzed the commits from `docker-rust` and `docker-rust-nightly` and found a set of contributors that made at least a single commit to these repositories. We used [this](https://gist.github.com/Kobzol/9a67009a40e6d91786fffd9a73ee5030) script for performing the analysis.Related issues: https://github.com/rust-lang/docker-rust/issues/206, https://github.com/rust-lang/docker-rust/issues/12, https://github.com/rust-lang/docker-rust-nightly/issues/14
PR with the new license: https://github.com/rust-lang/docker-rust/pull/74
Checkoff
To agree to the licensing terms, please comment with the following text on this issue (you can copy the text using the copy button on the right):
Thank you very much!
Affected contributors: