On Mon 28-Feb-2011 at 01:09 -0800, kfj wrote:
On 27 Feb., 23:00, Bruno Postle <[email protected]> wrote:
>What I mean is this: hsi, the python module that is generated by SWIG
>and contains the hugin functionality, can be imported by any python
>script that cares to do so. It's like loading a shared library from an
>executable program, in fact, technically, this is just what happens.
>But the code that finds it way into the script via this route is
>GPLed. Therefore, if I understand things rightly, the module would
>have to make itself known as GPL software, prohibit closed-source
>users to import it and point a way to it's sources, plus whatever
>other requirements the GPL imposes.
We would want people to write their own scripts and not care about
this stuff so long as they didn't distribute them.
I don't quite follow your train of thought here. What do you mean by
"so long as they didn't distribute them"?
Oops, I was responding to the idea that the plugin interface would
enforce the GPL in plugins programatically, but maybe that wasn't
what you were saying.
Any plugins that were distributed with Hugin would need to be GPL
too, or some more liberal license.
The module itself doesn't do any i/o though and can't communicate
it's license status. Is that okay with the GPL? Does there have to
be some mechanism to display the license or is it enough to have a
LICENSE file with the distribution?
It isn't necessary to display the license in the GUI, Hugin does
this but it is more of an advocacy/education thing.
Excellent. You may have seen my second posting where I described
my experience with merging the branch back. It seems painless, but
I only tested it on Linux, so there may be obstacles I'm not aware
of. Would it be useful if I did the merge again at some convenient
point in time and uploaded the patch?
If you are working with HG, you should be able to just pull updates
from the 'default' branch and never worry that your branch is
diverging.
The main worry we have about merging new features into the 'trunk'
is that in the past we have merged unfinished stuff that then held
up a release for months - Either the new feature needs to be
complete, or it needs to be unobtrusive.
--
Bruno
--
You received this message because you are subscribed to the Google Groups "Hugin and
other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
