Hi Carlo:

On Thu, Sep 9, 2010 at 6:30 AM, Carlo Marcelo Arenas Belon
<care...@sajinet.com.pe> wrote:

> why would we want to do that and throw away useful and time
> tested code? why would we do this in trunk destabilizing the

We didn't "throw away" any code.  The only thing I did was replace the
underlying templating engine TemplatePower with Dwoo.  Sure there are
minor syntax differences (eg. {cpu_num} to {$cpu_num} in template
files) between the two systems and some PHP code's logic needs to be
changed, but all in all it's not as major an overhaul (in terms of
modified PHP code) as you would think.

> development branch instead of in an independent branch which
> could be tested and validated before it gets merged into trunk
> if proven to at least be as usefull as the old code?, what is

Independent branches are for implementing features that would require
extended period of time (for instance the mod_perl branch I just
created).  AFAIK the TemplatePower replacement is already complete and
has already been independently reviewed by 2 Ganglia developers.  I'm
not saying that it's bug free, but I don't believe the checked in code
is any more/less destabilizing than any other code that has been
checked into trunk.  If there are bugs going forward, I will fix them.

> the scope of the work that is required on the templates and
> the rest of the PHP code to make this transition?

See above.

> and this doesn't make a difference at all AFAIK with the fact that
> templatepower is GPL and some of the PHP code LGPL (for a discusion
> on that read old threads on this issue) specially considering that
> the frontend code is not "linked" with anything else.

YAIANL (You and I are not lawyers), but LGPL should not be an issue,
but GPL is an issue.  I thought you would be in agreement here since
you brought this issue up 2 years ago:

http://www.mail-archive.com/ganglia-developers@lists.sourceforge.net/msg04129.html

The last word is that since we may not be able to re-license the code,
it would be best to replace the templating engine with a BSD-friendly
one, which is exactly what I did.  I am trying to ensure that our
entire code base is clear from any licensing ambiguity and that's why
I have also been cleaning up the COPYING files clarifying that we are
indeed licensed under the new/modified BSD license.  I believe
removing the GPL-licensed TemplatePower from our code base was the
last hurdle.

Regards,

Bernard

------------------------------------------------------------------------------
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful, 
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance. 
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to