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

[8/7] Relicense under dual MIT / Apache v2 #3230

Closed
Manishearth opened this issue Sep 27, 2018 · 16 comments
Closed

[8/7] Relicense under dual MIT / Apache v2 #3230

Manishearth opened this issue Sep 27, 2018 · 16 comments

Comments

@Manishearth
Copy link
Member

Manishearth commented Sep 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.

This issue is for folks who made pull requests after #3093 was opened.

See #3093 (comment)

@Manishearth Manishearth changed the title Relicense under dual MIT / Apache v2 [8/7] Relicense under dual MIT / Apache v2 Sep 27, 2018
@Manishearth
Copy link
Member Author

@JayKickliter accepted in #3195

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

PSeitz commented Sep 27, 2018

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

@vi
Copy link
Contributor

vi commented Sep 27, 2018

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

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

@yangby-cryptape
Copy link
Contributor

yangby-cryptape commented Sep 27, 2018

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

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

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

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

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

ms2300 commented Oct 2, 2018

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

@o01eg
Copy link
Contributor

o01eg commented Oct 4, 2018

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

@tommilligan
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
@joelgallant
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.

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
@JayKickliter
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
@sanmai-NL
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.

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