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

[6/7] Relicense under dual MIT / Apache v2 #3100

Closed
35 tasks done
Manishearth opened this issue Aug 27, 2018 · 37 comments
Closed
35 tasks done

[6/7] Relicense under dual MIT / Apache v2 #3100

Manishearth opened this issue Aug 27, 2018 · 37 comments

Comments

@Manishearth
Copy link
Member

Manishearth commented Aug 27, 2018

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 license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I'll be ticking off the boxes below as people turn up.

(You may wish to unsubscribe from this issue after leaving your comment)

@Bobo1239
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@AtheMathmo
Copy link
Contributor

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
@gibfahn
Copy link
Contributor

gibfahn commented Aug 27, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@chrisvittal
Copy link
Contributor

chrisvittal commented Aug 27, 2018 via email

@17cupsofcoffee
Copy link
Contributor

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
@shepmaster
Copy link
Member

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@jmquigs
Copy link
Contributor

jmquigs commented Aug 27, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
I also like beer. 🍻

@joeratt
Copy link
Contributor

joeratt commented Aug 27, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@sourcefrog
Copy link
Contributor

sourcefrog commented Aug 27, 2018 via email

@chrisduerr
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@CAD97
Copy link
Contributor

CAD97 commented Aug 27, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to choose either at their option.

@carols10cents
Copy link
Member

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
@michaelrutherford
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@pickfire
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@cesarb
Copy link
Contributor

cesarb commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@mhasbini
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@untitaker
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@badboy
Copy link
Member

badboy commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@lucab
Copy link
Contributor

lucab commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@caemor
Copy link
Contributor

caemor commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@JDemler
Copy link
Contributor

JDemler commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@hobofan
Copy link
Contributor

hobofan commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@vorner
Copy link
Contributor

vorner commented Aug 28, 2018

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)

@martinlindhe
Copy link
Contributor

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
@CYBAI
Copy link
Contributor

CYBAI commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@FauxFaux
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@clarfonthey
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@auscompgeek
Copy link
Contributor

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.)

@b-r-u
Copy link
Contributor

b-r-u commented Aug 28, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@Fraser999
Copy link
Contributor

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
@thekidxp
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@mati865
Copy link
Contributor

mati865 commented Sep 13, 2018

Pinging @EpicatSupercell @erickt @yaahallo @Jascha-N

@Jascha-N
Copy link
Contributor

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
@erickt
Copy link
Contributor

erickt commented Sep 17, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@EpicatSupercell
Copy link
Contributor

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@yaahc
Copy link
Member

yaahc commented Sep 22, 2018

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@Manishearth
Copy link
Member Author

Thanks, all! We've got all the sign offs on this issue, closing (see the #3093 if you'd like updates)

Manishearth added a commit that referenced this issue Oct 5, 2018
Documentation on relicensing in previous commit

Fixes #2885

Also fixes #3093, fixes #3094, fixes 3095, fixes #3096, fixes #3097, fixes #3098,
fixes #3099, fixes #3100, fixes #3230
Manishearth added a commit that referenced this issue Oct 5, 2018
Documentation on relicensing in previous commit

Fixes #2885

Also fixes #3093, fixes #3094, fixes 3095, fixes #3096, fixes #3097, fixes #3098,
fixes #3099, fixes #3100, fixes #3230
Manishearth added a commit that referenced this issue Oct 6, 2018
Documentation on relicensing in previous commit

Fixes #2885

Also fixes #3093, fixes #3094, fixes 3095, fixes #3096, fixes #3097, fixes #3098,
fixes #3099, fixes #3100, fixes #3230
Manishearth added a commit that referenced this issue Oct 6, 2018
Documentation on relicensing in previous commit

Fixes #2885

Also fixes #3093, fixes #3094, fixes 3095, fixes #3096, fixes #3097, fixes #3098,
fixes #3099, fixes #3100, fixes #3230
Manishearth added a commit that referenced this issue Oct 6, 2018
Documentation on relicensing in previous commit

Fixes #2885

Also fixes #3093, fixes #3094, fixes 3095, fixes #3096, fixes #3097, fixes #3098,
fixes #3099, fixes #3100, fixes #3230
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