On Apr 23, 2008, at 4:31 PM, Mike Howard wrote:

> On Sat, Apr 19, 2008 at 02:14:19AM -0500, Carlo Marcelo Arenas Belon  
> wrote:
>> most likely just a formality, as the web frontend templating system  
>> was based
>> on the GPLv2+ TemplatePower class from the very beginning (at least  
>> as
>> shown from the history in svn).
>>
>> a quick line count from the files involved says the contributers  
>> that will
>> need to consent will be (including number of lines committed from  
>> all files in
>> the web directory including non php files which could be as well  
>> discarded as
>> an alternative) :
>>
>>     38 bnicholes
>>     87 carenas
>>    410 knobi1
>>    426 bernardli
>>    686 hawson
>>    830 sacerdoti
>>   3940 massie
>
> I am not a lawyer, nor do I know anything specific about what  
> licencing
> agreements were made when Ganglia was released, but any code written  
> by
> Matt Massie while in the employment of UC Berkeley might be considered
> property of the UC Regents and he may not be able to authorize license
> changes.

hey mike, good to hear from you.  you're right that all the work i did  
while at berkeley is property of the UC Regents.  the issue here is  
about a PHP class i used as a template engine for building the web  
front-end.  i'm confident that we  can replace the template engine  
with a BSD friendly engine without angering the regent gods.  i want  
ganglia to continue, as it always has, being distributed as BSD code.

sorry guys that i missed the license on that file.

-matt



-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to