Do you want proprietary develpers to write plugins for Avogadro? If yes, I’d propose Java/Jambi binding (are there any obfuscators for Python? I don’t know any)
Regards,
Konstantin
On Wednesday 10 March 2010 05:07:42 Konstantin Tokarev wrote:
Do you want proprietary develpers to write plugins for Avogadro? If yes,
I’d propose Java/Jambi binding (are there any obfuscators for Python? I
don’t know any)
Not possible - GPL license includes any plugins as they link to Avogadro. This
is one of the large reasons I wanted an LGPL license, but as we link to
OpenBabel this is not possible.
Marcus
On Wednesday 10 March 2010 05:07:42 Konstantin Tokarev wrote:
Do you want proprietary develpers to write plugins for Avogadro? If yes,
I’d propose Java/Jambi binding (are there any obfuscators for Python? I
don’t know any)
Not possible - GPL license includes any plugins as they link to Avogadro. This
is one of the large reasons I wanted an LGPL license, but as we link to
OpenBabel this is not possible.
Couldn’t you release Avogadro’s headers under LGPL?
IMHO, if plugin doesn’t access OB, it doesn’t violate GPL
–
Regards,
Konstantin
On Wednesday 10 March 2010 11:27:28 Konstantin Tokarev wrote:
On Wednesday 10 March 2010 05:07:42 Konstantin Tokarev wrote:
Do you want proprietary develpers to write plugins for Avogadro? If
yes, I’d propose Java/Jambi binding (are there any obfuscators for
Python? I don’t know any)Not possible - GPL license includes any plugins as they link to Avogadro.
This is one of the large reasons I wanted an LGPL license, but as we
link to OpenBabel this is not possible.Couldn’t you release Avogadro’s headers under LGPL?
IMHO, if plugin doesn’t access OB, it doesn’t violate GPL
Your opinion is all fine and well, but in all of the research I did (fairly
extensive) along with the Qt, PyQt and FSF opinions, if you link to a GPL
library then the entire work must be licensed under the GPL (or something more
liberal) - see the viral nature of the GPL or copyleft.
Even the Python extensions/plugins are covered under the GPL. Doubly so when
using PyQt - that is a large reason why Nokia are sponsoring development of
PySide, an LGPL Python wrapper for Qt.
You could use a server/client arrangement, communicating with the library from
the plugin using a local TCP socket. There are some other options I believe,
but can’t think of them off the top of my head.
So in its current state proprietary plugins are not possible. GPL or more
permissively licensed. We could license our headers LGPL (or even all of
Avogadro) but the second Avogadro links to OpenBabel the entire work becomes
covered by the GPL. This is the major thing that the L in LGPL allows.
Marcus
On Mar 10, 2010, at 11:35 AM, Marcus D. Hanwell wrote:
Avogadro) but the second Avogadro links to OpenBabel the entire work becomes
covered by the GPL. This is the major thing that the L in LGPL allows.
Which is to say that if OB ever re-licenses, then Avogadro could also change its license.
My last comment – it’s perfectly fine to make a “personal” proprietary plugin. Let’s say in you code up something which access your company’s proprietary database. That’s perfectly allowable. I’ve imagined that there are people doing this already (BWH van Beest seems to be doing this.)
You just can’t distribute that proprietary plugin.
-Geoff
10.03.10, 11:35, “Marcus D. Hanwell” marcus@cryos.org:
On Wednesday 10 March 2010 11:27:28 Konstantin Tokarev wrote:
On Wednesday 10 March 2010 05:07:42 Konstantin Tokarev wrote:
Do you want proprietary develpers to write plugins for Avogadro? If
yes, I’d propose Java/Jambi binding (are there any obfuscators for
Python? I don’t know any)Not possible - GPL license includes any plugins as they link to Avogadro.
This is one of the large reasons I wanted an LGPL license, but as we
link to OpenBabel this is not possible.Couldn’t you release Avogadro’s headers under LGPL?
IMHO, if plugin doesn’t access OB, it doesn’t violate GPL
Your opinion is all fine and well, but in all of the research I did (fairly
extensive) along with the Qt, PyQt and FSF opinions, if you link to a GPL
library then the entire work must be licensed under the GPL (or something more
liberal) - see the viral nature of the GPL or copyleft.
Even the Python extensions/plugins are covered under the GPL. Doubly so when
using PyQt - that is a large reason why Nokia are sponsoring development of
PySide, an LGPL Python wrapper for Qt.
You could use a server/client arrangement, communicating with the library from
the plugin using a local TCP socket. There are some other options I believe,
but can’t think of them off the top of my head.
So in its current state proprietary plugins are not possible. GPL or more
permissively licensed. We could license our headers LGPL (or even all of
Avogadro) but the second Avogadro links to OpenBabel the entire work becomes
covered by the GPL. This is the major thing that the L in LGPL allows.
Marcus
[Crazy idea] What if Avogadro could use CDK backend as alternative for OB? It also support large number of formats, and is covered by LGPL
–
Regards,
Konstantin
Яндекс.Почта. Письма есть. Спама - нет. http://mail.yandex.ru/nospam/sign
Which is to say that if OB ever re-licenses, then Avogadro could also change its license.
I’ve remembered that symmetry code was licensed as GPL2+ by S.Patchkovskii. So, OB can’t be relicensed (
Regards,
Konstantin
I’ve remembered that symmetry code was licensed as GPL2+ by S.Patchkovskii. So, OB can’t be relicensed (
Sergei’s code is the least of the worries. He was pretty open to other licensing, the last I checked. Open Eye, on the other hand, won’t even change to “GPLv2+” rather than “GPLv2.”
Don’t worry. There are solutions. 
Cheers,
-Geoff
I’ve remembered that symmetry code was licensed as GPL2+ by S.Patchkovskii. So, OB can’t be relicensed (
Sergei’s code is the least of the worries. He was pretty open to other licensing, the last I checked. Open Eye, on the other hand, won’t even change to “GPLv2+” rather than “GPLv2.”
But I didn’t received any answer when I sent my modified code to him. Maybe his e-mail in the code is outdated though )
–
Regards,
Konstantin