Earlier quoted context omitted.
Yeah, I did not get that either. I also do not understand why the GPLv3 would necessitate a contributor agreement, but MIT would not. I always thought those agreements were necessary so that one institution has copyright and can change the license without getting approval from every author. That applies to any free license, doesn't it? Anyway, I think they just wanted to change to MIT before new authors commit withou…
The decisions were largely separate. The goal of having a CA was to leave us the option of selling commercial plugins in the future. We no longer plan to do that so we got rid of it. Separately, we kept hearing that the GPL is a hurdle to adoption at some companies so we switched to MIT.
Light Table 0.7.0
41–50 of 109 posts
Re: Light Table 0.7.0
#42I've considered using Light Table for a while but the fact that there isn't a simple way to install it on Linux (either via apt or another package manager or a packaged version like a deb/rpm) keeps me from bothering.
Re: Light Table 0.7.0
#43What issue could possibly exist for using a GPL editor? It's not being shipped from a company...
People rightly or wrongly don't feel comfortable modifying GPL code. And don't see any benefits to GPL. That seems pretty straightforward to me.
Re: Light Table 0.7.0
#44Earlier quoted context omitted.
You are definitely correct that some of the aversion is a knee jerk reaction and misunderstanding, but that aside, the MIT license is very end user friendly, more understood than the GPL, and more permissive to the end user, plus we kept hearing from folks that that's what they wanted, so we switched.
BSD is _developer_ friendly, not end-user friendly. In this case, your end users are developers, though... The GPL sacrifices developer freedoms for end-user freedoms. I don't think it's any inherently more or less free. But then you get into discussions of what 'freedom' means... I have written a ton of software licensed as each, and the tide is certainly turning toward the BSD. It just bums me out.
Re: Light Table 0.7.0
#45Earlier quoted context omitted.
Personally, I will not contribute to something that's GPLed unless it's really important project - the Linux kernel for example. I know a lot of other developers that think the same.
Why?
Re: Light Table 0.7.0
#46Earlier quoted context omitted.
Yeah, I did not get that either. I also do not understand why the GPLv3 would necessitate a contributor agreement, but MIT would not. I always thought those agreements were necessary so that one institution has copyright and can change the license without getting approval from every author. That applies to any free license, doesn't it? Anyway, I think they just wanted to change to MIT before new authors commit withou…
The decisions were largely separate. The goal of having a CA was to leave us the option of selling commercial plugins in the future. We no longer plan to do that so we got rid of it. Separately, we kept hearing that the GPL is a hurdle to adoption at some companies so we switched to MIT.
Re: Light Table 0.7.0
#47FWIW I remember trying LT once post-open sourcing and ran out of enthusiasm before I could figure out how to see any of the "cool stuff from the video".
Re: Light Table 0.7.0
#48What issue could possibly exist for using a GPL editor? It's not being shipped from a company...
Also, if you make a web-based product based on this, and a customer insists on hosting it in its cloud (many do because they do not want to, or in practice aren't allowed to, let their data out of their systems), can you sell it?
In both cases, did your patents just get free for all to use?
The moment you let in GPL code, you either give up having non-GPL code in your company, or you have to start spending time keeping the GPL and non-GPL code apart. If you do the latter, it also affects your flexibility.
Re: Light Table 0.7.0
#49Re: Light Table 0.7.0
#50I wonder how many people contributed under the assumption that their contributions would remain under GPL. I assume the CLA specifies their right to change the license?