The Apache License is a bit better protected against abuse/misuse than the MIT, and will probably be fit better for a growing project like Charset.

License: https://www.apache.org/licenses/LICENSE-2.0

Contributors so far:

@blay09
@rubensworks
@SoniEx2

Please respond with something along the lines of: "I agree to license all my contributions to Charset under the terms of the Apache License, version 2.0."

(This should go a bit easier than BuildCraft.)

I agree to license all my contributions to Charset under the terms of the Apache License, version 2.0.

I agree to license all my contributions to Charset under the terms of the Apache License, version 2.0.

(Quick question, aren't you allowed to mix Apache licensed code and MIT licensed code? :P)

yes, but why gplv2 over gplv3?

On Tue, 24 May 2016 at 08:56 Soni L. [email protected] wrote:

I did say GPLv2, not GPLv2+

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#68 (comment)

No Tivoization clause, usually, which is only useful if you're a hardware manufacturer.

I agree to license my CODE REMOVAL... wait... can you even license code removal????

Better safe than sorry.

I agree to dual-license all my contributions to Charset under the terms of the Apache License, version 2.0, and the Boost Software License, version 1.0.

@SoniEx2

what

no

@asiekierka Your fault for choosing a dumb license.

@SoniEx2 I'll just revert your commit

I just want charset to stay MIT :(

@SoniEx2 it's not MIT right now because none of the contributions are MIT. they never were.

I don't like the apache license 2.0, any other option?

@SoniEx2 , you really want to start complaining about the license? You have removed 1 freaking line...

@GirafiStudios this isn't about MY contributions, this is about my ability to reuse charset code.

And why can't you? Apache is plenty reusable.

On Tue, 24 May 2016, 8:10 AM Soni L. [email protected] wrote:

@GirafiStudios https://github.com/GirafiStudios this isn't about MY
contributions, this is about my ability to reuse charset code.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#68 (comment)

Not with GPLv2, not with MIT

Not even the MIT is reuseable with the MIT - you legally need to include every MIT license header from every project whose code you incorporate (which is why Charset distributes three MIT license files).

Can we relicense to WTFPL instead? :v

I like my licenses slightly more serious

2016-05-24 0:32 GMT+02:00 Jędrzej [email protected]:

Can we relicense to WTFPL instead? :v

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#68 (comment)

Why not pubdom it then, eh

Well, BSL is reusable with BSL and MIT... What about that?

apache is usable with GPLv3?

On Tue, 24 May 2016 at 08:46 Soni L. [email protected] wrote:

Well, BSL is reusable with BSL and MIT...

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#68 (comment)

I did say GPLv2, not GPLv2+

fd6af04