Problems, problems. Which I really hate to bring up as I want Roller to succeed as an Apache project as much as anyone.

http://svn.apache.org/repos/asf/incubator/roller/trunk/tools/lib/

We have 4 LGPL (ekit, ekit-applet, jazzy, mm.mysql), 2 BCL (mail, activation) jars in there.

http://svn.apache.org/repos/asf/incubator/roller/trunk/tools/hibernate-3.0/lib/

jta and jdbc-stdext are BCL.

http://svn.apache.org/repos/asf/incubator/roller/trunk/tools/hibernate-3.0/

hibernate is LGPL.

----

So at least 5 LGPL jars and 4 BCL jars. As far as I know, we're not meant to have these in SVN, and that the imports on the LGPL jars are not meant to be in SVN either.

Now I know that this was well known before Roller joined, so what's the status of this? What I've read on legal-discuss/board is not the same as the message we're giving Roller, so I'm confused. On roller-dev, Noel has said:

"Check with Cliff, but I believe that projects will be given a timeframe with which to eliminate LGPL dependencies. It isn't a legal (as in viral) so much as policy issue. We would certainly need appropriate notices, in addition to the Incubator disclaimer."

As far as I know, that's for the imports not for the inclusion in distributions/SVN. It's also going through one of its customary dead-in-the-water periods regarding becoming new policy.

We (roller-dev) will also need the Incubator PMC to create 'appropriate notices', depending on what you mean by that. [I'm a part of both, so this isn't me shirking work :) ].

So what's the deal? How do I make a release of Roller, ie) what needs to be different from a normal release; and how do I explain this to Cliff without it sounding like we're ignoring the lawyers.

Hen

Reply via email to