GPL is perfectly fine. It's a good match for something like LightTable. However companies that practice dual-licensing and that require copyright assignment for contributions do not have to play by the same rules as the third-parties that are contributing and I think this is poisonous.
It's a good business strategy of course, however, how many times have you heard of such a company that does profit sharing with the third-parties that contributed code? It's also bad for the company ... if some third-party releases some really good plugin as GPL, without doing copyright assignment, then it means the plugin in question will never be a part of the official distribution, which hurts all parties.
This is why I prefer the open core model, in which anybody can build proprietary things on top. For example IntelliJ IDEA Community Edition is licensed with the Apache 2.0 license. Apache 2.0 is IMHO the best open-source license. IntelliJ IDEA Ultimate edition includes all kinds of smarts and JetBrains is doing well - it obviously doesn't hurt them when third-parties release plugins such as this one: http://cursiveclojure.com/ - it actually helps them, because they don't have the resources to build plugins for everything under the sun.
BTW - I'm happy that LightTable was released as open-source. I would have preferred another license, preferably one that is compatible with EPL (that's pervasive in Clojure's ecosystem), but can't complain, it's their right to do as they please.
I know x264 (and upcoming x265) uses this method to make money off their open source software, they release it for anyone to use under GPL but also offer licences for those who wants to use it in proprietary projects.
AFAIK the money made is shared amongst x264 key contributors, but I have no idea if any money trickles down to less prolific contributors.
> if some third-party releases some really good plugin as GPL, without doing copyright assignment, then it means the plugin in question will never be a part of the official distribution,
Why not? I don't see why a third-party plugin should be excluded from the official open source distribution? Obviously they can't offer a proprietary licence for it alongside their own code, but it could still be part of the official release.
>This is why I prefer the open core model, in which anybody can build proprietary things on top.
Hmm... actually I prefer that if someone should make money off proprietary use of open source code, then it should be the authors of that open source code, so personally I prefer the dual-licence mechanism that the x264 devs use.
Anyone can use x264 in full open source fashion under GPL, if someone wants to use their work for proprietary means, the x264 developers are compensated for allowing this.
GPL is perfectly fine. It's a good match for something like LightTable. However companies that practice dual-licensing and that require copyright assignment for contributions do not have to play by the same rules as the third-parties that are contributing and I think this is poisonous.
It's a good business strategy of course, however, how many times have you heard of such a company that does profit sharing with the third-parties that contributed code? It's also bad for the company ... if some third-party releases some really good plugin as GPL, without doing copyright assignment, then it means the plugin in question will never be a part of the official distribution, which hurts all parties.
This is why I prefer the open core model, in which anybody can build proprietary things on top. For example IntelliJ IDEA Community Edition is licensed with the Apache 2.0 license. Apache 2.0 is IMHO the best open-source license. IntelliJ IDEA Ultimate edition includes all kinds of smarts and JetBrains is doing well - it obviously doesn't hurt them when third-parties release plugins such as this one: http://cursiveclojure.com/ - it actually helps them, because they don't have the resources to build plugins for everything under the sun.
BTW - I'm happy that LightTable was released as open-source. I would have preferred another license, preferably one that is compatible with EPL (that's pervasive in Clojure's ecosystem), but can't complain, it's their right to do as they please.