On Wed, 9 Mar 2005, Ceki [iso-8859-1] G�lc� wrote:
I am quite embarrassed to ask but what is the foundation's position on distributing code which depends on the following environments?

- Mono 1.0 (GPL)
- Microsoft .NET Framework 1.0 & 1.1 & Compact Framework 1.0 (Closed Source)
- Microsoft SSCLI 1.0 (Shared Source)

It's not a problem, even if it's a runtime dependency. The only problem arises if the use of any third-party software during development, build, or use has an effect on the license of the Apache work itself, usually by saying the Apache work is a "derivative work". A simple dependency would not cause that. Bundling one of those in with a release almost certainly would, and our current policy (IIRC) is to not redistribute separate third-party works from apache.org machines, even if they are under open source licenses.


It seems very similar to the situation encountered by all our projects based on the Java language which is licensed under somewhat ambiguous terms.

There is no risk in simply implementing your own ideas in Java. It's the implementation of specifications, be they OASIS or JCP or defined where ever, that one should think about the IP issues involved.


Nicko Cadell has compiled a list [1] of additional log4net dependencies. Could someone of a higher authority confirm that they are OK? In particular, log4net is built using GPL-licensed Nant, is that a problem from the foundation's point of view?

[1] http://marc.theaimsgroup.com/?l=log4net-dev&m=111037622301905&w=2

It's not a problem. (An aside - let me get this straight - someone took Ant, converted it from Java to C#, and relicensed under the GPL? The nerve of some people!). However, to clarify:


The release package includes project files for Microsoft Visual Studio
.NET, however this is not a dependency.

Does this mean these are files copied from (perhaps modified, perhaps not) the Microsoft product, which originally carried a Microsoft copyright? Or are these freshly created files simply designed to work with VS.NET?


        Brian

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to