Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Replace GPL license with the new EULA
- Loading branch information
Showing
727 changed files
with
1,459 additions
and
3,851 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:'(
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akien-mga yeah, I know, anyway people can still compile the program for their own personal purposes. The only restriction is that redistribution is not allowed. In my experience, the GPL license wasn't beneficial for us. Mainly because Linux distribution don't make it clear that they aren't associated in any form with the original developer of each application (and other issues). I'll write more about this in these days.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @dacap, I contribute to free software projects (Blender mostly) and also make things & code as an individual. Licensing choices are tough and I'm eager to read your views leading to this decision.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sadly this also will mean people will not optimized packages for their distributions.
I bought and also contributed (as sirlbackheart) to asperite but still prefer to get the software trough my distributions package repository in contrast to steam or compiling it myself.
I wonder what this new EULA means for Arch User Repository or similar things.
In that case no binary is distributed but only a script file that compiles and packages aseprite locally.
While sad to see you have to take this stepp I understand that you tried to walk the line between having this project fully open source and to make a living out of working on your project.
As mentioned by @significant-bit it will be interesting to read what led to this decision.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@raetiacorvus hi sirlbackheart, in the case of Arch User Repository, you should be able to still distribute the script. The code will be available to download and compile it locally, so if the script does that, it's just fine.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The point of GPL is to be beneficial for the users, not for the developpers.
I don’t see who could believe a Linux distribution to be associated with all the software available as packages for it, that does not seem plausible at all. I’m not sure I see what kind of harm it would do anyway.
So for comparison, do you see something that other software repositories like Apple Store and others do that make the distinction more visible than with GNU/Linux package repositories?
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you'll see in the future that:
False excuse, there is no relationship with open source.
If you want to avoid the confusion with a version you distribute, you can forbid distros to use the name of your software, that's enough (this was done by a product owner called Mozilla for a product called Firefox, Debian used the name Iceweal instead and it was clear enough that bugs in distros are not always bugs in Debian; but actually this is no more the case because both parties discussed and found that it is better for everyone that software is in distros, with the right name).
GPL (and open source) is actually focused on users, who may not appreciate to lose the easiness of hacking it and redistribute it.
That said, "it was not good for us" is not really a reason for removing something, I would have expected an explanation more like "it was bad for us because (...)" (= how did they harm you?).
That's a pity that open source loses a software. But thanks to open source, the main developer can not decide alone of the fate of a software (this is the reason open source is useful), and users can decide too. I hope that the open source version replaces the non open source version as e.g. X.org replaced XFree when XFree86 decided to change the license to a non open source license (or maybe the main developer will change in mind about open source?)
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is like saying "I hope you die." Now I know from which side I want to be.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are looking from a developer point of view.
I look from a potential user and from the software points of view, for end user rights, and open source addict: someone wants to kill an open source app (the patch you applied killed an open source app), I hope that the open source software will live.
Maybe the GPL was not the right license for you, because it looks like you are not interested in the freedom of you users. That's a pity.
You misinterpreted my sentence: I just hope that you put back the software in open source, and if it is unfortunately not possible I hope that the open source version keeps living. Nothing about dying except something you did yourself.
Having the main repo back to open source would be the best option, of course.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, as a user I can still download the source, compile them, use the program, I'm ok with that. And I can do whatever I want of the sources as long as I don't redistribute the modifications and the binaries.
With the GPL I can do whatever I want of the sources as long as I don't redistribute the modifications and the binaries as well. If I want to redistribute the modifications, I must comply with the GPL strict requirements (for example keep the licence as GPL, I'm not free to change to licence, or I'm not free to redistribute the modified sources without the binaries)
Thank you @dacap for making aseprite Open Source!
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The statement that this software is open source in README.md is not true as the EULA conflicts with the Open Source Definition (https://opensource.org/docs/osd) on several points.
That statement should be removed or changed, as this right now is proprietary software with viewable source code from what I can understand, calling it open source will just confuse and mislead your users.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the words @farvardin
@olji I'll fix that issue today
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Dillybob92 that might be an option, yes
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing that's a bit confusing... it seems there were other contribuiters (http://www.aseprite.org/contributors/ and possibly others through code submitted via github issues) to this project who made their contributions to a GPL project. Did you have them all assign copyright to you or remove their changes, before attempting to change the license?
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same for the FAQ, "If Aseprite is open source, (...)" is no more true.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trusting this comment, there was a CLA so that's legal.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's right @JeromeMartinez and @gerrywastaken, the CLA was made to sublicense Aseprite (mainly to create an iOS version of Aseprite, which I've never started yet).
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes you can @Dillybob92
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aeris I didn't contact all developers yet, anyway we have a CLA to sublicense code (created to a possible iOS version of Aseprite).
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just posted comments about this in the Aseprite devblog: http://dev.aseprite.org/post/149797781837/new-source-code-license
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry @TheMatrixShibe, we have a code of conduct too.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@remi6397 You can distribute it as of the parent of this commit, or the GPL fork: https://github.com/aseprite-gpl/aseprite/
But you can't distribute the current master of aseprite/aseprite. AFAIK @dacap owns all the copyright on Aseprite thanks to his CLA, so he can revoke the GPL from this commit onwards as he did.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@remi6397 "I'm sure that CLA doesn't apply in this case." licenses are already a complex item and source of conflict, no need to make it even more complex by having wrong guesses. If contributors signed a CLA (looks like it is the case), all the contributors already gave the right to change the license (it is exactly the purpose of a CLA).
In other words, you have the right to distribute with GPL terms the version before this commit, and no right to do so on this commit and all the new ones, if you redistribute this project (master) under the terms of GPL, you just do counterfeiting, whatever you imagine.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Unfortunately, terms of GPL apply over CLA." I have no idea how you can imagine that, but it is 100% wrong (basically, the CLA is exactly designed for letting the project owner decides of the license of the project, the term of a CLA is that the code owner permits the person who gets the CLA to relicense in any term he wants: the code owner still have the right to distribute his part, and only his part, in whatever icense he wants, but that does not change the fact that the person who gets the CLA to relicense), please stop propagating wrong things, it is already complex enough with reality.
Note that I previously said that the license change is done for bad reasons, but thinking that does not prevent me to correctly understand what is a CLA.
What you don't understand is that the GPL does not apply anymore, so we don't care of the design of GPL here (for master version), the GPL is designed for protecting what is delivered in GPL, that's all. Here newest versions are not under GPL (and it is legal due to CLA), whatever you imagine.
And whatever you think about this issue, it would still be counterfeiting to put "GPL" on code you don't own, if you think the project owner (and me, and a lot of other people include persons in charge of license in distros) are wrong, you need to go to court for forcing the project owner to change the license back (spoiler: you will be rejected immediately, only the code owner can go to court, you have no right at all about that)
You should review your thoughts about licenses, you are twice wrong (one about CLA, one about forcing GPL on code you don't own because you think it is the actual license).
Again, the disagreement is already complex, no need to make it even more complex with wrong assumptions.
And now, you can not say that you didn't know that it is wrong if you redistribute the project (after this commit) with GPL license.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have a serious problem with understanding licenses, you add a new mistake at every answer (the last one is giant), I give up trying to explain.
Summary: if you do what you imagine (I can still redistribute this project after this commit under the terms of GPL), you do counterfeiting whatever you imagine.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GPL applied to the code, not the project.
The GPL hasn't been revoked.
It has simply never been applied to the post-license-change code.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
He isn't using GPL code.
He's using code he owns or has the granted right to license as he chooses.
The fact that he also chose to license much of the code as GPL is completely irrelevant.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What don't you understand with the fact that everyone already agreed? (hint: CLA)
So you say the project owner can't relicense and that he can relicense in the same page, just crazy.
No. Even without CLA (code owner, and in any case not you because you have no right on that, would have to go in court for forcing the project owner to publish with GPL respecting the license he received, else you do counterfeiting even if you are right about the issue).
There were already several cases about that, please stop propagating wrong guesses about something you have difficulties to understand. You are trolling, and you are a typical example about the reason a lot of people prefer to stay away for open source.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You still have the same problem : here, it is not the case, classic way for CLA is that the code owner provide the code with CLA, then the project owner distribute with GPL. If you don't understand that, you can not understand everything about licenses.
You still speak about GPL when it does not apply anymore, legally (CLA), just stop: either you are a code owner who has not signed any CLA with project owner and you can go in court, either you have no right for forcing GPL here.
I understand very well, you are trying (very badly, with a mistake in nearly every sentence) to convince yourself that you would have the right to redistribute under GPL, without taking care about the fact you have absolutely no right on that. This is sadly a classic thing from copyleft fans.
A peaceful discussion is not possible when one has only one goal (e.g. having something not GPL to be GPL) without trying to understand legal things.
and whatever you think about CLA, you have 0 right to do so, only the code owner could complain about their code, and in court only. Again, you are just trying to convince yourself that you would not do counterfeiting, but it is really a bad method for open source (you are jut hurting open source when you do that, open source opponents just say thank you to you).
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still wrong: if you find one who did not sign the CLA, the project owner does counterfeiting, but it does not make the project GPL, whatever you imagine.
Again and again, another mistake about license.
AFAIK, the CLA was needed for being accepted in this repo.
Now, stop trolling and find one person who did not sign (good luck, because if it was the case the person would have already said it)
When someone does a mistake about license at every post, it is difficult to stay calm.
The truth was already there 2 years ago, only you has difficulties to accept it.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in case you are interested in truth (I doubt), you don't need to get ownership transfer ("CAA"), a right to relicense is enough ("CLA"), when you want to relicense (case here), surprised about that?
http://wiki.civiccommons.org/Contributor_Agreements/
You demonstrated again that you have prejudices about licensing, imagining that the project owner needs any ownership transfer for relicensing.
"The uncomfortable truth".
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@remi6397 the code is no longer GPL since this commit (it was relicensed), so you cannot redistribute it under GPL terms. Please contact me at davidcapello@gmail.com or support@aseprite.org if you want to discuss this.
5ecc356
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@remi6397 just a note, licensing something under GPL doesn't make you lose your copyright (you can always alter the license of your work in the future and enforce other license), that's why the FSF make you sign a copyright assignment when you contribute to GNU software.
Aseprite code was written by myself and was licensed under GPL, contributors signed a CLA so their contributions could be relicensed, then I relicensed the code to the new EULA (or MIT license). I hope this information help you to understand this issue.