Closed hazzik closed 10 years ago
I'm sorry, but I don't see where you're coming from. Are you afraid of getting sued for using jekyll-tagging
? Don't be.
There are so many points to discuss, I don't even know where to start. So I'll spare us both the pain unless you really want to get into it ;)
The issue is not about being sued of whatever. The issue is about incorrectly applied license.
The other possible solution is dual licensing of nuggets
to MIT
The issue is about incorrectly applied license.
And that concerns you how? I'm just trying to understand why you opened this issue in the first place. What's your stake here?
Also, it's only your opinion. I, for one, don't see using another library as constituting a derived work. I'm probably in the minority with that view, but I'm certainly not alone.
Ok, in the future, please read FAQ on GPL first, before applying the license.
http://www.gnu.org/licenses/gpl-faq.html#GPLWrapper
I'd like to incorporate GPL-covered software in my proprietary system. Can I do this by putting a “wrapper” module, under a GPL-compatible lax permissive license (such as the X11 license) in between the GPL-covered part and the proprietary part? (#GPLWrapper) No. The X11 license is compatible with the GPL, so you can add a module to the GPL-covered program and put it under the X11 license. But if you were to incorporate them both in a larger program, that whole would include the GPL-covered part, so it would have to be licensed as a whole under the GNU GPL.
And AGPL reuires to release sources even I do not do any distribution.
And there I thought we could have an honest discussion about this - important - topic...
@pattex: I'm out. Feel free to continue any way you'd like.
@blackwinter No thanks, this smells a little much like simple trolling.
jekyll-tagging is "released" under MIT license, however it has dependencies on
ruby-nuggets
ornuggets
which licensed as AGPL. Sojekyll-tagging
should be licensed as AGPL as well or should not depend on nuggets./cc @blackwinter