Good point, Could you please send it to locationTech mainlinglist too. Thanks a lot Frank
2012/10/5 Chris Holmes <[email protected]>: > On further reading I now understand that the EDL is _exactly_ the BSD, > with just 'eclipse' filled in for the organization. > > But I do think it's important to refer to it in the source code > headers and in front pages and the like as BSD, since many more people > will instantly recognize it. But for the actual license text can just > use the EPL text. > > (on a side note, I think Eclipse could much improve their license > positioning by pointing out on the EDL page that the license is > exactly the BSD license with no modifications except that Eclipse is > named as the organization). > > On Fri, Oct 5, 2012 at 8:52 AM, Chris Holmes <[email protected]> wrote: >> I think it'd be good to clarify if the dual is EPL & EDL or _actually_ >> EPL & BSD. >> >> I'd strongly recommend actually doing BSD. EDL is 'just like' BSD for >> sure, comes out the same in all the compatibility stuff, but much of >> the world does not actually know what it is. Does not have the same >> 'brand recognition' as BSD. I think to get the most people to >> understand it should actually be BSD. >> >> Case in point: https://www.google.com/search?q=edl >> >> BSD is an approved LocationTech license, so I don't believe it should >> be a problem at all. >> >> On Fri, Oct 5, 2012 at 3:34 AM, Jody Garnett <[email protected]> wrote: >>> Page is updated (with dual license example) >>> - http://udig.refractions.net/confluence/display/UDIG/License+Change >>> - https://jira.codehaus.org/browse/UDIG-1952 >>> >>> If I can ask you to review the page? And then you or jesse can make the >>> motion to go with dual EPL & EDL approach (either on email or IRC). When >>> making a motion on email please use a new subject line :D >>> >>> -- >>> Jody Garnett >>> >>> On Friday, 5 October 2012 at 5:12 PM, Frank Gasdorf wrote: >>> >>> 1+ I second the EPL BSD aproach! Sounds we going to have a >>> license-conform workflow for rapidly prototyping in uDig and move code >>> to core modules of geotools afterwards. >>> >>> Frank >>> >>> 2012/10/5 Jesse Eichar <[email protected]>: >>> >>> Hi, >>> >>> The last email about a double-license, EPL BSD. Sounds like a good idea to >>> me as it makes porting code from uDig to Geotools pretty straightforward and >>> easy. I think it is time for the final decision. >>> >>> @Jody Could you do a quick write up about the new licensing? >>> >>> Jesse >>> >>> _______________________________________________ >>> User-friendly Desktop Internet GIS (uDig) >>> http://udig.refractions.net >>> http://lists.refractions.net/mailman/listinfo/udig-devel >>> >>> _______________________________________________ >>> User-friendly Desktop Internet GIS (uDig) >>> http://udig.refractions.net >>> http://lists.refractions.net/mailman/listinfo/udig-devel >>> >>> >>> >>> _______________________________________________ >>> User-friendly Desktop Internet GIS (uDig) >>> http://udig.refractions.net >>> http://lists.refractions.net/mailman/listinfo/udig-devel >>> _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
