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.

Sign up for GitHub

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

Jump to bottom

[7/7] Relicense under dual MIT / Apache v2 #3099

Closed
33 tasks done
Manishearth opened this issue Aug 27, 2018 · 36 comments
Closed
33 tasks done

[7/7] Relicense under dual MIT / Apache v2 #3099

Manishearth opened this issue Aug 27, 2018 · 36 comments

Comments

@Manishearth
Copy link
Member

Manishearth commented Aug 27, 2018 •
edited
Loading

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)
@Manishearth Manishearth mentioned this issue Aug 27, 2018
Closed
@sunjay
Copy link
Member

sunjay commented Aug 27, 2018

I am unable to check myself off for whatever reason, but I am fine with this.

Unsubscribing, so @ me if needed. :)

@Rantanen
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
@letheed
Copy link

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

@upsuper
Copy link
Contributor

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

@reujab
Copy link
Contributor

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

@utam0k
Copy link
Contributor

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

@musoke
Copy link
Contributor

musoke commented Aug 27, 2018 via email

@upsuper
Copy link
Contributor

upsuper commented Aug 27, 2018

(Please don't reply via the email, or if you reply via email, strip the quoted content, otherwise you'll @ everyone in the list again and bring them back to subscription of this thread.)

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

@scottmcm
Copy link
Member

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

@lo48576
Copy link
Contributor

lo48576 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
@quininer
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.

@budziq
Copy link
Contributor

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

@zayenz
Copy link
Contributor

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

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

@ghost
Copy link

ghost commented Aug 28, 2018 •
edited by ghost
Loading

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

@Vlad-Shcherbina
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
@Ms2ger
Copy link
Contributor

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

@Keats
Copy link

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

@senden9
Copy link
Contributor

senden9 commented Aug 28, 2018 •
edited
Loading

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

@josephDunne
Copy link
Contributor

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

@shahn
Copy link
Contributor

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

3 similar comments
@pietro
Copy link
Contributor

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

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

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

@reiner-dolp
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.

@dereckson
Copy link
Contributor

I don't think my contribution is above the https://en.wikipedia.org/wiki/Threshold_of_originality to make this necesserary, but if it helps your relicensing operation, I'm glad to comply.

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

@debris
Copy link
Contributor

debris commented Sep 3, 2018

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

@pgerber
Copy link
Contributor

pgerber commented Sep 10, 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 @PixelPirate @mrmonday @steveklabnik @zmt00

@PixelPirate
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
@steveklabnik
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.

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

@dereckson
Copy link
Contributor

I've sent a mail to @zmt00, as apparently they aren't currently active on GitHub.

@Manishearth
Copy link
Member Author

While their sign off would be nice to have, their contribution was a typo fix so it's not strictly necessary.

Which means this issue is done! Thanks, all! You can follow the progress on this in #3093

Manishearth added a commit that referenced this issue Oct 5, 2018
@Manishearth
Relicense clippy
97f5561 
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
@Manishearth
Relicense clippy
f43007b 
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
@Manishearth
Relicense clippy
c3bfdfb 
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
@Manishearth
Relicense clippy
d3e8585 
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
@Manishearth
Relicense clippy
ca437e8 
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
@Vlad-Shcherbina Vlad-Shcherbina mentioned this issue Dec 22, 2018
Merged
bors added a commit that referenced this issue Dec 22, 2018
@bors
Auto merge of #3573 - Vlad-Shcherbina:map_clone_caveat, r=flip1995
52820e5 
Document map_clone known problems #498

(cherry picked from commit ada0d2c)

This was lost in relicensing (057243f).
However, I [acknowledged](#3099 (comment)) relicensing so this cherry pick should be fine I guess.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests