Forums

AD> The license of the trunk should be LGPL as Sara
AD> pointed out. For my branch I would like to stick with
AD> GPL. This shouldn't be a problem.

I haven't had time to look at the code in the repository,
but do beware of one thing:

Under USA copyright laws, if you have code under GPL 2.0
licensing and then use it as part of other code, then the
other code must be distributed under the same licensing
terms. This is the "viral" nature of GPL 2.0. It is not
possible under those terms, as I understand them, to take
code that is GPL 2.0 licensed, expand it or use it as part
of another larger program, and change the license to LGPL
for subsequent distribution. The larger program is,
according to the licensing terms, bound to be licensed under
GPL terms too.

Everyone, please be careful about the starting points for
this. If there's GPL'ed code in the repository that's part
of jsbml, the whole thing must then be put under GPL. The
only way around it (in my admittedly limited understanding)
is to not use the GPL'ed code as part of the distribution.

Be especially careful about simply changing the headers of
source code files to say "LGPL".

MH

____________________________________________________________
To manage your jsbml-development list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/jsbml-development

For a web interface to the jsbml-development mailing list, visit
http://sbml.org/Forums/

For questions or feedback about the jsbml-development list,
contact sbml-team@caltech.edu