On Fri, 14 Oct 2005 01:17:02 -0400 Jose O Gonzalez <[EMAIL PROTECTED]> babbled:

> 
> 
> On Fri, 14 Oct 2005 12:19:14 +0900 Carsten writes:
> > On Thu, 13 Oct 2005 16:51:23 -0500 Nathan Ingersoll 
> > <[EMAIL PROTECTED]>
> > babbled:
> > 
> > > 
> > > Looking ahead, if Simon and Hisham are committed to working as 
> > part of the
> > > team, one excellent way to extend an olive branch would be to BSD 
> > license
> > > their theme. With the heavy GTK influence I can understand Simon's
> > > reluctance to use a different license, but that only covers the 
> > code, not
> > > the theme. I did a quick port of their theme to EWL and it looked 
> > pretty
> > > damn good, but there's no chance of this work going into the EWL 
> > theme
> > > unless that license is changed. The way the two use edje is too 
> > different at
> > > this time to make themes that can be effectively shared between 
> > the two, but
> > > I don't see why some sharing can't occur at this level. ETK has 
> > the benefit
> > > of using EWL code without fear of license complications, it would 
> > be nice if
> > > EWL could do the same with the ETK theme.
> > 
> > i do think that is a major issue. you dont license something the 
> > same as
> > another project just because the other project heavily influenced 
> > its design
> > and ideas and structure. license applies to COPIES, not influences, 
> > ideas,
> > inspiration. it has to be pretty much a direct copy (and then a 
> > derivative from
> > there). i agree that etk, being lgpl, is not productinve in terms of 
> > it being
> > able to share back. i know i dont plan on even thinking of "blessing 
> > it" even
> > as official competition - if there can be such a thing (you get the 
> > idea) as
> > long as it's lgpl. it basically stands out as a sore thumb in cvs 
> > and i 100%
> > agree with everyone (except simon) on this issue. it should be 
> > changed just so
> > it can be shared - you can share themes (well take the theme and 
> > adapt for
> > ewl), or you can find useful code in etk and use it in ewl, and 
> > vice-versa.
> > 
> 
>       It's odd but one begins to get the feeling that a lot of this
> negative reaction to etk has more to do with the licensing issue
> than with actual code, or antecedent discussion about issues,
> etc.
> 
>       I personally fail to understand the free-and-good-BSD vs
> political-and-bad-LGPL, stance of many here.
> 
>       The reality is that *any* recourse to a license, even a copyright,
> is taking a political stance - it is seeking protection through the legal
> framework via some scheme.
> 
>       To brand one such scheme as political but another as free of
> politics is illusory.
> 
>       I personally do not care much for any licensing schemes, and
> every piece of code I've ever put up here, meager as it's been, I've
> done so with no conditions whatever - I've not copyrighted anything,
> I've not licensed anything, I've not asked for my name to be added
> to any list of contributors, I've not asked for anything to be 'applied'
> or for 'access to cvs'...
> 
>       If others have the view that they would prefer their work to
> be protected under the legal framework afforded by use of copyright
> and/or a choice of license then that is something I very much respect.
>       But villifying one license scheme as 'political' and blessing
> another as the one true 'apolitical' choice, is quite flawed.
> 
>       If indeed there are those who care about "choice" above all,
> then either place no constraints on your work, or allow for a choice
> of licensing schemes - allow for the work to be licensed under a number
> of licenses that are commonly used: BSD, GPL, XYZ, ...

indeed it is their choice - 100% their choice. the reasonings for that choice
may be partly flawed (imho) but still their choice, BUT, because of the
license, it basically creates a 1 way doorway to that bit of code from the rest
of the code that is bsd licensed. if they know that and know the result will
basically be that no one works with the lgpl code either in contributing or
using it, then that's fine. but it is an issue if they wish for more than
that. :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [EMAIL PROTECTED]
裸好多
Tokyo, Japan (東京 日本)


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to