>It's the third variation that makes no sense to me. I just don't think that's >correct. Jmol is a library. All they are requiredto do is publish the changes >to the Jmol library. The whole purpose of "Lesser" is that they don't need to >publish their code. That's all.
I'm not saying they have to publish their code ... just that is is ONE of the possible ways of meeting the obligation outlined in section 2 of the LGPL, Conveying Modified Versions: http://www.gnu.org/licenses/lgpl.html#section2 >Features that involve "new ways of communicating with or interacting with >...." where is this last part coming from: "...new features in LGPL work must >work and be understandable and extendable to another user without access to >closed-source work."? Why do you say any of that? What specifically are you >imagining there? Is that language from the license? see link above ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Jmol-developers mailing list Jmol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-developers
