[Savannah-hackers] Re: Fwd: Re: submission of OpenEXR high dynamic range (HDR) image f - savannah.gnu.org

[Mathieu Roy]

Drew Hess <address@hidden> a tapoté :

> Hi Mathieu,
> 
> Do I need to re-register the OpenEXR project on Savannah, or was it 
> already set up the previous time that I registered?

No, you need to re-register.

Regards,


> 
> thanks -dwh-
> 
> On 17 Dec 2002, Mathieu Roy wrote:
> 
> > 
> > Hi,
> > 
> > 
> > According to
> > http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses
> > the license you chose is GPL-compatible. So your project can now be
> > hosted on Savannah.
> > 
> > Regards,
> > 
> > Drew Hess <address@hidden> a tapoté :
> > 
> > > Hello,
> > > 
> > > I'm happy to announce that ILM has changed the license for OpenEXR.  
> > > We're now using the Modified BSD license.  Please have a look at the text
> > > of our new license, provided below.  We want to ensure that this license 
> > > is GPL-compatible.
> > > 
> > > thanks
> > > -dwh-
> > > 
> > > -----
> > > 
> > >                 Copyright (c) 2002, Industrial Light & Magic, a division
> > > of Lucas Digital Ltd. LLC
> > >                 All rights reserved.
> > > 
> > >                 Redistribution and use in source and binary forms, with or
> > > without modification, are permitted provided that the following conditions
> > > are met:
> > >                         * Redistributions of source code must retain the
> > > above copyright notice, this list of conditions and the following
> > > disclaimer.
> > >                         * Redistributions in binary form must reproduce
> > > the above copyright notice, this list of conditions and the following
> > > disclaimer in the documentation and/or other materials provided with the
> > > distribution.
> > >                         * Neither the name of Industrial Light & Magic nor
> > > the names of its contributors may be used to endorse or promote products
> > > derived from this software without specific prior written permission.
> > >                 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
> > > CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
> > > NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> > > A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
> > > OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
> > > EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
> > > PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
> > > PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
> > > LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
> > > NEGLIGENCE OR OTHERWISE)  ARISING IN ANY WAY OUT OF THE USE OF THIS
> > > SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> > > 
> > > On 23 Aug 2002, Free Software Foundation wrote:
> > > 
> > > > One such example is:
> > > > 
> > > > 3.3. Description of Modifications.
> > > > You must cause all Covered Code to which You contribute to contain a
> > > > file documenting the changes You made to create that Covered Code and
> > > > the date of any change. 
> > > > 
> > > > The GPL does not require this (although it does require something
> > > > similar).  The same is true of sections 3.5 and 6 -- they are similar to
> > > > the GPL, but different enough to be incompatible.
> > > > 
> > > > 
> > > > On Thu, 2002-08-22 at 11:25, Mathieu Roy wrote:
> > > > > 
> > > > > NOTE for the address@hidden PEOPLE:
> > > > > Can you help us, give advices? Thanks a lot for your attention.
> > > > > 
> > > > > This is the summary of the problem:
> > > > > Drew Hess want to host his project on savannah.
> > > > > His company choose a MPL 1.1-like license. 
> > > > > On the licenses-list page, it talks about "complex restrictions" : Can
> > > > > you enumerate these restrictions for Drew? 
> > > > > 
> > > > > 
> > > > > > Hi Mathieu,
> > > > > 
> > > > > Hi Drew
> > > > > 
> > > > > Note: you should received an empty message. I made a little mistake.
> > > > > 
> > > > > > > > I'm not familiar with ILM Public License. As far I
> > > > > > > > understand, it's
> > > > > > > > based on MPL 1.1.
> > > > > > 
> > > > > > Yes, that's right.
> > > > > 
> > > > > > > > If you're willing to switch to a GPL-compatible
> > > > > > > > license,
> > > > > > > > or dual-licensing with a GPL compatible license
> > > > > > > > (if your license is MPL 1.1 on based on it), please
> > > > > > > > resubmit.
> > > > > > > > (additionally, we would like you to list
> > > > > > > > differencies between ILMPL
> > > > > > > > and MPL 1.1)
> > > > > > > > 
> > > > > > > > You can get a list of various licenses and comments
> > > > > > > > about them at
> > > > > > > > http://www.gnu.org/philosophy/license-list.html 
> > > > > > > > that should help you to understand our position.
> > > > > > 
> > > > > > Unfortunately the URL you refer to only mentions the "complex 
> > > > > > restrictions 
> > > > > > that make it incompatible with the GNU GPL."  That's not very 
> > > > > > helpful when 
> > > > > > I try to explain to our lawyers why I want to change our license, 
> > > > > > or 
> > > > > > dual-license our code.
> > > > > > 
> > > > > > I'm sympathetic to the FSF and GNU (L)GPL, and I would really like 
> > > > > > to host 
> > > > > > our site at Savannah rather than Sourceforge, but it won't be 
> > > > > > sufficient 
> > > > > > to tell the legal department that the Open Source license they've 
> > > > > > crafted 
> > > > > > isn't going to work because of "complex restrictions."  Can you 
> > > > > > enumerate 
> > > > > > these restrictions for me?  Our legal department has been very 
> > > > > > cooperative 
> > > > > > and eager to create a license that allows us (for the first time 
> > > > > > ever) to 
> > > > > > publish our source code as Free Software, and they might be willing 
> > > > > > to 
> > > > > > listen if I have good reasons to make further changes.
> > > > > 
> > > > > Good.
> > > > > 
> > > > > > I'll ask the legal department for the list of exactly what they 
> > > > > > changed 
> > > > > > vs. the MPL 1.1.  Their chief concern was that the license 
> > > > > > explicitly not 
> > > > > > grant use of ILM trademarks when distributing or using OpenEXR 
> > > > > > software.  
> > > > > > I believe that's the only material change versus the MPL 1.1.
> > > > > > 
> > > > > > Assuming the legal department is willing to make changes, is it 
> > > > > > sufficient
> > > > > > for a license to be compatible with the GNU LGPL in order to host at
> > > > > > Savannah?  I assume yes, since the LGPL must be compatible with the 
> > > > > > GPL.
> > > > > 
> > > > > Right too. The most frequently used licenses on Savannah are GPL and
> > > > > mBSD (modified BSD).
> > > > > 
> > > > > 
> > > > > > One of the main reasons we're releasing this code is to encourage
> > > > > > commercial software vendors to use it in their applications,
> > > > > > e.g. Adobe Photoshop and Alias|Wavefront Maya.  This is beneficial
> > > > > > to our company because we use these tools for our work, and in many
> > > > > > cases there are no Free Software applications that provide
> > > > > > equivalent functionality.  For that reason, we won't be able to
> > > > > > release OpenEXR under the GNU GPL, because no commercial software
> > > > > > company link this code into their (proprietary) applications.  But
> > > > > > the LGPL would be fine.
> > > > > 
> > > > > Choosing GPL or LGPL is matter of strategy. There's a page that give
> > > > > hints http://www.gnu.org/philosophy/why-not-lgpl.html
> > > > > 
> > > > > 
> > > > > > We've already done that (using our own license instead of the GPL), 
> > > > > > but
> > > > > > you're welcome to look at our work.  You can obtain it at
> > > > > > ftp://warehouse.lucasdigital.com/OpenEXR-0.9.tar.gz. 
> > > > > 
> > > > > Ok.
> > > > > 
> > > > > 
> > > > > Regards,
> > > > > 
> > > > > -- 
> > > > > Mathieu Roy
> > > > >  
> > > > >  << Profile  << http://savannah.gnu.org/users/yeupou <<
> > > > >  >> Homepage >> http://yeupou.coleumes.org           >>
> > > > >  << GPG Key  << http://gpg.coleumes.org              <<
> > > > 
> > 
> > 

-- 
Mathieu Roy
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<