-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[6/7] Relicense under dual MIT / Apache v2 #3100
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
Comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
1 similar comment
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
1 similar comment
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
10 similar comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. (Technically, my only contribution was the rust-update script, that is likely outdated and unneeded as clippy is now installed by rustup) |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
3 similar comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
Hm. Given my only contribution has been 9bb68b8, can I just do this instead? I waive any and all copyright claims on my past contributions. (I really feel like holding a copyright claim on a pair of parentheses is a bit silly.) |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
1 similar comment
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
Pinging @EpicatSupercell @erickt @yaahallo @Jascha-N |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
2 similar comments
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option. |
Thanks, all! We've got all the sign offs on this issue, closing (see the #3093 if you'd like updates) |
This is one of the sub-issues for relicensing this repo to MIT / Apache v2, the license used by most of the Rust ecosystem. For more information, see #3093
To agree to relicensing, comment with :
I'll be ticking off the boxes below as people turn up.
(You may wish to unsubscribe from this issue after leaving your comment)
The text was updated successfully, but these errors were encountered: