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

License under dual MIT/Apache-2.0 #175

Closed
16 tasks done
est31 opened this issue Nov 29, 2022 · 17 comments
Closed
16 tasks done

License under dual MIT/Apache-2.0 #175

est31 opened this issue Nov 29, 2022 · 17 comments

Comments

@est31
Copy link
Member

est31 commented Nov 29, 2022

This is an issue to license the rust-lang/fmt-rfcs repo under dual Apache2 OR MIT licensing terms. Currently there is no license file in this git repository, I have made a draft PR for Apache2 OR MIT licensing terms: #174

You are receiving this notification because you have contributed to this repo.

Checkoff

To agree to the licensing terms, please comment in this thread with:

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

Thank you! ❤️

For general comments, given the number of people subscribed to this issue, I recommend keeping discussion to the PR in #174 or the zulip topic. Thanks!

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

14 similar comments
@Rufflewind
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.

@CYBAI
Copy link
Contributor

CYBAI commented Nov 29, 2022

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

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

@kraai
Copy link
Contributor

kraai commented Nov 29, 2022

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

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

@nrc
Copy link
Member

nrc commented Nov 29, 2022

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

@daniel-vainsencher
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.

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

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

@ahl
Copy link
Contributor

ahl commented Nov 29, 2022

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

@solson
Copy link
Member

solson commented Nov 30, 2022

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

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

@strega-nil
Copy link

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

@camelid
Copy link
Member

camelid commented Dec 17, 2022

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

@est31
Copy link
Member Author

est31 commented Dec 18, 2022

I'm closing this as resolved, as all authors have given their consent.

Thanks again! ❤️

Archived link

@est31 est31 closed this as completed Dec 18, 2022
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