2010/1/7 Seif Lotfy <s...@lotfy.com>:
> Here is how i see it. More People use our code the more consultancy we can
> provide even for proprietary.

Yes, but I think you are mixing up "linking" and "copying".

Proprietary applications *can* use Zeitgeist (be it over D-Bus, the
Python module or whatever). What they cannot do is take source code
from Zeitgeist and copy it into their project unless it's
{L,}GPLv3{,+}  (eg. they cannot take Zeitgeist and make a proprietary
version out of it, or take our algorithms -once we have something...
*sigh*- and modify them to work in their proprietary application).

If we switch to LGPLv2.1+ nothing of the above changes, the only
difference is that they can copy stuff into {L,}GPLv2{,+} applications

Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer       363DEAE3

License change "LGPL 3" to "LGPL 2.1 or later"
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.

Status in Zeitgeist Framework: New

Bug description:
There's a push to change the license of the codebase from "LGPL 3" to "LGPL 2.1 
or later".

As it stands we have full consent from Seif Lotfy and Mikkel Kamstrup. 
Siegfried Gevatter has made a conditional +1:

  "If _everyone_ else wants to switch from "LGPL3 or later" to "LGPL 2.1or 
later", I'm fine with it."

Of the core contributors Markus Korn has not answered yet.

If Markus agrees the next logical step is to create a list of other 
contributors we have that should be heard.

Mailing list: https://launchpad.net/~zeitgeist
Post to     : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help   : https://help.launchpad.net/ListHelp

Reply via email to