On Sat, 07 May 2005 09:14:46 -0600 Tres Melton <[EMAIL PROTECTED]> babbled:

> On Sat, 2005-05-07 at 04:17 -0400, Mike Frysinger wrote:
> > On Saturday 07 May 2005 03:53 am, Mike Frysinger wrote:
> > > i just see it as an annoying issue where you suddenly cant assume that you
> > > can copy & paste code from any old random e17 app into any other random 
> > > e17
> > > app
> > 
> > after a quick chat with Simon, why not have a general rule with e17:
> > - libraries are BSD
> > - apps can be GPL/whatever, but you should add an exception clause that 
> > says 
> > that e17 devs can import code from your GPL/whatever app into their app 
> > without having to worry about stupid licensing conflicts
> > 
> > > side note, doing a quick check on all the COPYING files, these are GPL:
> > > e17/libs/esmart
> > > e17/libs/epsilon
> > > e17/proto/exml
> > 
> > since these are libraries and GPL-2 sucks for libraries, perhaps this was 
> > just 
> > a copy & paste error and these really should be BSD ?
> > -mike
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: NEC IT Guy Games.
> > Get your fingers limbered up and give it your best shot. 4 great events, 4
> > opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> > win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> > _______________________________________________
> > enlightenment-devel mailing list
> > enlightenment-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 
> This is kinda important to me as well.  I am finishing up a SSE2 port of
> Eterm's shading routines and wanted to use the GPL license for them.  I
> didn't even realize that E/Eterm uses the BSD license.  I would prefer
> the code stay open with the GPL but if MeJ insists then I suppose the
> BSD license will have to do.  It's his baby after all.  I just like
> things to go fast!  ;-)

well you could make them GPL - but mej can just not accept the patches as they 
would taint eterm's existing license making it gpl. bsd guarantees that THAT 
code stays open - but if people can steal it - if i want to "steal" that code 
and put it into some closed proprietary project - you would never know. it can 
be reformatted, and at the end of the day its an algorithm. there are only so 
many ways you can write a fast routine to do a fairly narrow scoped task. if 
that was the case someone would have claimed copyright infringement on for (i = 
0; i < n; i++) a long time ago :)

anyway - i can understand what you mean - but even if it were gpl you couldn't 
practically find instances of it in closed code :(. you will know your code 
will be public and free in eterm's code and available and able to be re-used 
with very few restrictions, but not more limitations than that.

basically if someone submits patches to code - they are implicitly agreeing to 
the existing copyright license unless they ask for a change or re-license their 
patches and code. if they are licensed differently the chances of them being 
used drop dramatically to somewhere about 0 :(

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


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to