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

[4/7] Relicense under dual MIT / Apache v2 #3097

Closed
29 of 30 tasks
Manishearth opened this issue Aug 27, 2018 · 30 comments
Closed
29 of 30 tasks

[4/7] Relicense under dual MIT / Apache v2 #3097

Manishearth opened this issue Aug 27, 2018 · 30 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)

@alexheretic
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.

1 similar comment
@illicitonion
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.

@Twisol
Copy link
Contributor

Twisol 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. 🙂

choose

FTFY!

@alexreg
Copy link
Contributor

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

@dtolnay
Copy link
Member

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

@swgillespie
Copy link
Contributor

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

@kraai
Copy link
Contributor

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

@waywardmonkeys
Copy link
Contributor

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

@U007D
Copy link

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

5 similar comments
@apasel422
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.

@ishitatsuyuki
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.

@kennytm
Copy link
Member

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

@scurest
Copy link
Contributor

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

@nrc
Copy link
Member

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

@alusch
Copy link
Contributor

alusch commented Aug 28, 2018

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

@siiptuo
Copy link
Contributor

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

4 similar comments
@karyon
Copy link
Contributor

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

@danieledapo
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.

@imp
Copy link
Contributor

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

@ghost
Copy link

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

@skade
Copy link
Contributor

skade commented Aug 28, 2018

While I don't follow cmr's argument, I see the value in consistency.

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

@MaloJaffre
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.

6 similar comments
@utaal
Copy link
Contributor

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

@inrustwetrust
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.

@alexeyzab
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.

@AlexEne
Copy link
Member

AlexEne commented Aug 29, 2018

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

@chyvonomys
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.

@kvikas
Copy link
Contributor

kvikas commented Sep 11, 2018

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 @F001 @wartman4404

@F001
Copy link
Contributor

F001 commented Sep 14, 2018

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

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