[Mulgara-dev] License Question.

[Andrae Muys]

On 24/10/2006, at 9:12 AM, Ian Boston wrote:
> Brian Sletten wrote:
>> My understanding of that clause is that it is if you pull software  
>> (Java code) out of Mulgara (not simply use the public APIs) the  
>> software you remove or it's mutated form (Java files) maintain  
>> their license. The mutated forms (of those files, not your  
>> project) maintain their original license.
>> That is certainly our intent. Dave Wood or someone who has spent  
>> more time reading through these licenses will comment in the near  
>> future, I am sure, but it is not our intent (nor my understanding)  
>> that our license is viral; it is just sticky.
>> We are pleased to have a cool project like Sakai looking to use  
>> our store.
>> Let us know if you have any issues,

It is certainly our intent and belief that as long as you use the  
designated public API's (currently those are the Session API, the  
Resolver SPI, and the Security SPI) you can use Mulgara in any  
project you like.

My understanding of the license is that:
Any changes you make to Mulgara are naturally affected.
Any changes that make use of internal API's would make your  
application a derivative work and therefore trigger 1c.

David Wood will no doubt comment further on this as he did a lot of  
the research that led to the adoption of the MPL originally, and the  
OSL recently.

Of course none of us are lawyers around here.

Andrae

-- 
Andrae Muys
andrae at netymon.com
Principal Mulgara Consultant
Netymon Pty Ltd