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

Relicense under dual MIT/Apache-2.0 #161

Closed
16 of 18 tasks
est31 opened this issue Aug 22, 2019 · 18 comments · Fixed by #163
Closed
16 of 18 tasks

Relicense under dual MIT/Apache-2.0 #161

est31 opened this issue Aug 22, 2019 · 18 comments · Fixed by #163

Comments

@est31
Copy link
Contributor

est31 commented Aug 22, 2019

Hi, it would be cool to relicense tiny-http under the dual license terms MIT OR Apache-2.0 (at the choice of the licensees) that are common in the Rust community.

To signify consent, please comment with the following:

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

Thanks!

Contributor checkoff:

@Eijebong
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

14 similar comments
@frewsxcv
Copy link
Member

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@zaneli
Copy link
Contributor

zaneli commented Aug 22, 2019

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@mb64
Copy link
Contributor

mb64 commented Aug 22, 2019

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@moises-silva
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@tomprogrammer
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@romanz
Copy link
Contributor

romanz commented Aug 22, 2019

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@ashleysommer
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@djc
Copy link
Contributor

djc commented Aug 22, 2019

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@nikolaplejic
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@ordepdev
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@algesten
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@ebfe
Copy link
Contributor

ebfe commented Aug 27, 2019

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@PENGUINLIONG
Copy link
Contributor

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@tomaka
Copy link
Member

tomaka commented Sep 24, 2019

I agree with relicensing my contributions to this work to the dual MIT/Apache-2.0 license.

@est31
Copy link
Contributor Author

est31 commented Sep 24, 2019

Friendly reminder to @spk @erickt @phildawes : could you please check whether you want to agree to this relicensing?

Also, their contributions seem fairly small so maybe we can just go forward with the relicensing.

@phildawes
Copy link
Contributor

phildawes commented Sep 24, 2019 via email

est31 added a commit to est31/tiny-http that referenced this issue Oct 9, 2019
This performs the relicensing to MIT/Apache-2.0 as discussed in tiny-http#161
(archived link: http://web.archive.org/web/20191009143715/https://github.com/tiny-http/tiny-http/issues/161)

Instead of updating the file headers, I just removed them,
as the rustc compiler has done the same: rust-lang/rust#57108
@pinkforest
Copy link

There is a dependency chunked-transfer that is only Apache 2.0 licensed, re-license here:

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

Successfully merging a pull request may close this issue.