commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning P. Schmiedehausen" <...@intermeta.de>
Subject Licensing (was: Re: [configuration] handling exceptions in AbstractConfiguration implementations)
Date Wed, 06 Oct 2004 22:13:30 GMT
"Eric Pugh" <epugh@upstate.com> writes:

>This is really driving me crazy..  I have tracked threads on general and
>jakarta-pmc mailing lists about this..  And everytime it comes down to "I am
>not a lawyer" and a bunch of FUD.  We really need someone from the top of
>Apache to provide direction.  I work a lot with hibernate code and can think
>of at least 4 projects that have hibernate code in them (at least as far as
>import statements).

There _is_ a clear statement from the board. And even though we don't
really like it technology-wise, it is sound from a licensing point of
view.

#1 "No LGPL dependencies in code delivered from *.apache.org"

#2 "import <xxx>" where <xxx> is a LGPLed package is already a dependency.

I think that Geir made this clear on general@.

So every project that does have e.g. Hibernate dependencies in there
must move off-Apache. This holds true for some maven-plugins and it
would also hold true for a possible Hibernate-related
commons-configuration module.

This is not a bad thing IMHO. Apache is mainly about community and the
drive to keep the "sources clean".

Having some modules or code being outside apache.org (e.g. on
SourceForge) shouldn't be a big problem. We add a "links to related
stuff" to the site and everything is fine.

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

"Fighting for one's political stand is an honorable action, but re-
 fusing to acknowledge that there might be weaknesses in one's
 position - in order to identify them so that they can be remedied -
 is a large enough problem with the Open Source movement that it
 deserves to be on this list of the top five problems."
                       -- Michelle Levesque, "Fundamental Issues with
                                    Open Source Software Development"

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message