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

[2/4] License under dual MIT/Apache-2.0 #2077

Closed
40 tasks done
Tracked by #43461
est31 opened this issue Jul 25, 2017 · 42 comments
Closed
40 tasks done
Tracked by #43461

[2/4] License under dual MIT/Apache-2.0 #2077

est31 opened this issue Jul 25, 2017 · 42 comments
Labels
T-core Relevant to the core team, which will review and decide on the RFC.

Comments

@est31
Copy link
Member

est31 commented Jul 25, 2017 •
edited
Loading

This is a sign-off issue as per RFC 2044 (tracking issue) to license the rust-lang/rfcs repo under dual Apache2/MIT licensing terms.

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

For a discussion on why this move is desired, please see the RFC's text.

While smaller changes can't be copyrighted by law, its non-trivial to find out with certainity whether a given change falls under copyright or not, due to the nature of the matter. Therefore I'm asking you to agree to the new terms even if you consider your contributions to be not copyrightable.

To minimize noise in your inbox, let me use this opportunity to ask those among you who have unmerged RFCs in the queue to add a license header to your RFC drafts. In a few days/weeks I'll go through the list of open RFCs and ask for license headers to be added for the remaining RFCs that lack headers. The RFC's text contains the precise header (and has one already itself). Filing PRs to add headers to your already merged RFCs is not required, they will get headers in bulk.

Checkoff

To agree to the licensing terms, please comment 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!
@eminence
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
@KodrAus
Copy link
Contributor

KodrAus commented Jul 25, 2017

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

@est31 est31 mentioned this issue Jul 25, 2017
Open
7 tasks
@sophiajt
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
@krdln
Copy link
Contributor

krdln commented Jul 25, 2017

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

@durka
Copy link
Contributor

durka commented Jul 25, 2017

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

@japaric
Copy link
Member

japaric commented Jul 25, 2017

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 Jul 25, 2017

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

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

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

@IonoclastBrigham
Copy link
Contributor

IonoclastBrigham commented Jul 25, 2017 via email

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

18 similar comments
@ipetkov
Copy link
Contributor

ipetkov commented Jul 25, 2017

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

@Gankra
Copy link
Contributor

Gankra commented Jul 25, 2017

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

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

@flugsio
Copy link
Contributor

flugsio commented Jul 25, 2017

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

@glebm
Copy link
Contributor

glebm commented Jul 25, 2017

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

@F001
Copy link
Contributor

F001 commented Jul 25, 2017

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

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

@Havvy
Copy link
Contributor

Havvy commented Jul 25, 2017

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

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

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

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

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

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

@iopq
Copy link
Contributor

iopq commented Jul 25, 2017

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

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

@Kimundi
Copy link
Member

Kimundi commented Jul 31, 2017

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

@lambda
Copy link
Contributor

lambda commented Jul 31, 2017

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

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

JinShil commented Aug 2, 2017

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

@Gankra
Copy link
Contributor

Gankra commented Aug 2, 2017

(note for records: @huonw has contacted the core team and provided his consent in private)

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

@est31 est31 mentioned this issue Aug 5, 2017
Closed
24 tasks
@Hywan
Copy link
Contributor

Hywan commented Aug 7, 2017

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

@est31
Copy link
Member Author

est31 commented Aug 13, 2017

Friendly ping:

@extesy
Copy link
Contributor

extesy commented Aug 14, 2017

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
@Fraser999
Copy link

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 Oct 19, 2017

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

@LeoTestard
Copy link
Contributor

LeoTestard commented Oct 29, 2017 •
edited
Loading

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

@eminence
Copy link
Contributor

Everyone signed off! 🎉 🎉 👏

@est31
Copy link
Member Author

est31 commented Oct 29, 2017

Everybody: Thank you very much. I can close this issue as resolved then!

@est31 est31 closed this as completed Oct 29, 2017
@Centril Centril added the T-core Relevant to the core team, which will review and decide on the RFC. label Feb 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-core Relevant to the core team, which will review and decide on the RFC.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests