licenses (was Re: riakkit, a python riak object mapper, has hit beta!(
Andrey V. Martyanov
realduke at gmail.com
Fri Mar 2 05:24:45 EST 2012
Sorry for the late response, I didn't see your message! In fact, I know
the differences between the two. But, what is the profit of using it? Why
don't just use BSD, for example, like many open source projects do. The
biggest minus of LGPL is that many people think that it's the same as GPL
and have problems understanding it. Even your think that I don't know the
difference! :) Why? Because, it's a common practice. A lot of people really
don't know the difference. That's why I said before that (L)GPL is
overcomplicated. If you open the LGPL main page , first thing you will
see is "Why you shouldn't use the Lesser GPL for your next library". Is it
normal? It confuses people. There are a lot of profit in pulling back the
changes you've made - a lot of people see it, fix it, comment it, improve
it and so on. Why the license forces me to to that? It shouldn't.
On Fri, Mar 2, 2012 at 8:29 AM, Justin Sheehy <justin at basho.com> wrote:
> Hi, Andrey.
> On Mar 1, 2012, at 10:18 PM, "Andrey V. Martyanov" <realduke at gmail.com>
> > Sorry for GPL, it's a typo. I just don't like GPL-based licenses,
> including LGPL. I think it's overcomplicated.
> You are of course free to dislike anything you wish, but it is worth
> mentioning that GPL and LGPL are very different licenses; the LGPL is
> missing infectious aspects of the GPL.
> There are many projects which could not use GPL code compatibly with their
> preferred license but which can safely use LGPL code.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users