/amethyst

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-license Apache2 and MIT #28

Closed
thiolliere opened this Issue Mar 13, 2016 · 19 comments

Comments

Assignees
No one assigned
Labels
Projects
  
Shipped in Engine
Milestone
  1.0
@thiolliere

thiolliere commented Mar 13, 2016

as you may know rust libraries are mostly dual-licensed in apache-MIT

The Apache license has protections from patent trolls and an explicit contribution licensing clause.
And the MIT is for GPLv2 compatibility (because Apache is not compatible with GPLv2)

here a message from a crate.io bot for explanation of how to set dual-license in your project.

feel free to close it if your intension is to keep MIT alone.

Anyway great project, keep going :-)

@ebkalderon ebkalderon added diff: easy type: task status: in-progress pri: normal labels Mar 14, 2016

@ebkalderon ebkalderon added this to the 1.0 milestone Mar 14, 2016

@ebkalderon

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Mar 14, 2016

Member

@thiolliere Thanks for pointing this out! I didn't really think about patent trolls and explicit contribution licensing when I first started the project, since I wasn't really sure if people were interested in helping or not. This seems like a good idea to me. Hopefully everyone else agrees.

Contributor checkoff

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.

Or, if you're a contributor (looks like GitHub only shows contributors to master), you can check the box in this repo next to your name.
Member

ebkalderon commented Mar 14, 2016 •
edited by White-Oak
Edited 1 time
  • @White-Oak White-Oak edited Oct 27, 2016 (most recent)

@thiolliere Thanks for pointing this out! I didn't really think about patent trolls and explicit contribution licensing when I first started the project, since I wasn't really sure if people were interested in helping or not. This seems like a good idea to me. Hopefully everyone else agrees.

Contributor checkoff

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.

Or, if you're a contributor (looks like GitHub only shows contributors to master), you can check the box in this repo next to your name.

@ebkalderon ebkalderon changed the title from relicense under dual-license apache2 and MIT to Relicense under dual-license Apache2 and MIT Mar 23, 2016

@ebkalderon

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Jul 19, 2016

Member

@Aceeri @cooperra @csherratt @nchashch @Oflor The source code is changing at a growing rate, and we need everyone on this list to chime in whether you support this transition. This has been sitting here for far too long now, we should arrive at a consensus ASAP.
Member

ebkalderon commented Jul 19, 2016 •
edited
Edited 1 time
  • @ebkalderon ebkalderon edited Jul 19, 2016 (most recent)

@Aceeri @cooperra @csherratt @nchashch @Oflor The source code is changing at a growing rate, and we need everyone on this list to chime in whether you support this transition. This has been sitting here for far too long now, we should arrive at a consensus ASAP.
@Aceeri

This comment has been minimized.

Show comment
Hide comment
@Aceeri

Aceeri Jul 19, 2016

Member

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

Aceeri commented Jul 19, 2016

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

This comment has been minimized.

Show comment
Hide comment
@nchashch

nchashch Jul 19, 2016

Member

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

nchashch commented Jul 19, 2016

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jul 21, 2016

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

ghost commented Jul 21, 2016

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

This comment has been minimized.

Show comment
Hide comment
@cooperra

cooperra Jul 22, 2016

Contributor

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

cooperra commented Jul 22, 2016

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

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Sep 8, 2016

Member

@Emilgardis @lschmierer @LucioFranco @Oflor @palodequeso @serprex @White-Oak Please respond to this thread whether you support the licensing change or not. As contributors to this repository, your input is very valuable, and this thread cannot be closed until you chime in. Thanks!
Member

ebkalderon commented Sep 8, 2016 •
edited
Edited 1 time
  • @ebkalderon ebkalderon edited Sep 9, 2016 (most recent)

@Emilgardis @lschmierer @LucioFranco @Oflor @palodequeso @serprex @White-Oak Please respond to this thread whether you support the licensing change or not. As contributors to this repository, your input is very valuable, and this thread cannot be closed until you chime in. Thanks!
@White-Oak

This comment has been minimized.

Show comment
Hide comment
@White-Oak

White-Oak Sep 8, 2016

Contributor

My contribution to amethyst was pretty minor and I hope i can contribute more :), but, nevertheless, I checked myself in in that list.

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

White-Oak commented Sep 8, 2016 •
edited
Edited 1 time
  • @White-Oak White-Oak edited Sep 8, 2016 (most recent)

My contribution to amethyst was pretty minor and I hope i can contribute more :), but, nevertheless, I checked myself in in that list.

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

This comment has been minimized.

Show comment
Hide comment
@lschmierer

lschmierer Sep 8, 2016

Member

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

lschmierer commented Sep 8, 2016

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

This comment has been minimized.

Show comment
Hide comment
@Emilgardis

Emilgardis Sep 9, 2016

Contributor

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

Emilgardis commented Sep 9, 2016

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

This comment has been minimized.

Show comment
Hide comment
@palodequeso

palodequeso Sep 9, 2016

Contributor

My contribution to amethyst was pretty minor and I hope i can contribute more :), but, nevertheless, I checked myself in in that list.

Ditto, although I've recently started looking into adding SteamVR support again. :)

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

palodequeso commented Sep 9, 2016 •
edited
Edited 1 time
  • @palodequeso palodequeso edited Sep 9, 2016 (most recent)

My contribution to amethyst was pretty minor and I hope i can contribute more :), but, nevertheless, I checked myself in in that list.

Ditto, although I've recently started looking into adding SteamVR support again. :)

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

This comment has been minimized.

Show comment
Hide comment
@LucioFranco

LucioFranco Sep 9, 2016

Member

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

LucioFranco commented Sep 9, 2016

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

This comment has been minimized.

Show comment
Hide comment
@serprex

serprex Sep 9, 2016

Contributor

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

serprex commented Sep 9, 2016

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

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Oct 12, 2016

Member

@msiglreith @Oflor Please chime in on whether you agree or disagree with this relicensing initiative! Thank you.
Member

ebkalderon commented Oct 12, 2016

@msiglreith @Oflor Please chime in on whether you agree or disagree with this relicensing initiative! Thank you.
@msiglreith

This comment has been minimized.

Show comment
Hide comment
@msiglreith

msiglreith Oct 12, 2016

Contributor

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

msiglreith commented Oct 12, 2016

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

This comment has been minimized.

Show comment
Hide comment
@Emilgardis

Emilgardis Oct 17, 2016

Contributor

It seems like @Oflor hasn't been active in a long time.
Contributor

Emilgardis commented Oct 17, 2016

It seems like @Oflor hasn't been active in a long time.
@Oflor

This comment has been minimized.

Show comment
Hide comment
@Oflor

Oflor Oct 18, 2016

Contributor

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

Oflor commented Oct 18, 2016

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

This comment has been minimized.

Show comment
Hide comment
@Emilgardis

Emilgardis Oct 27, 2016

Contributor

Anyone doing work for the relicense? Seems like everyone is onboard. master on amethyst/website also needs to be changed to state that we are dual-licensed
Contributor

Emilgardis commented Oct 27, 2016

Anyone doing work for the relicense? Seems like everyone is onboard. master on amethyst/website also needs to be changed to state that we are dual-licensed
@Aceeri

This comment has been minimized.

Show comment
Hide comment
@Aceeri

Aceeri Oct 27, 2016

Member

I can do this later if no one else wants to.
Member

Aceeri commented Oct 27, 2016

I can do this later if no one else wants to.

@Aceeri Aceeri referenced this issue Oct 28, 2016

Merged

Dual-license Apache and MIT #126

@Aceeri Aceeri closed this Nov 21, 2016

@ebkalderon ebkalderon added status: resolved and removed status: in-progress labels Feb 1, 2017

@ebkalderon ebkalderon added this to Shipped in Engine Feb 3, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment