Обсуждение: software license question
A question came up on the jdbc mail list today that I couldn't answer.
It involves some code that is in the jdbc cvs tree (and has been for
many releases). This code contains the following license terms in each
file:
/*
* Redistribution and use of this software and associated documentation
* ("Software"), with or without modification, are permitted provided
* that the following conditions are met:
*
* 1. Redistributions of source code must retain copyright
* statements and notices. Redistributions must also contain a
* copy of this document.
*
* 2. 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.
*
* 3. The name "Exolab" must not be used to endorse or promote
* products derived from this Software without prior written
* permission of Exoffice Technologies. For written permission,
* please contact info@exolab.org.
*
* 4. Products derived from this Software may not be called "Exolab"
* nor may "Exolab" appear in their names without prior written
* permission of Exoffice Technologies. Exolab is a registered
* trademark of Exoffice Technologies.
*
* 5. Due credit should be given to the Exolab Project
* (http://www.exolab.org/).
*
* THIS SOFTWARE IS PROVIDED BY EXOFFICE TECHNOLOGIES AND CONTRIBUTORS
* ``AS IS'' AND ANY EXPRESSED 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
* EXOFFICE TECHNOLOGIES OR ITS 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.
*
* Copyright 1999 (C) Exoffice Technologies Inc. All Rights Reserved.
*
Is this a problem?
thanks,
--Barry
Barry Lind wrote: > > A question came up on the jdbc mail list today that I couldn't answer. > It involves some code that is in the jdbc cvs tree (and has been for > many releases). This code contains the following license terms in each > file: > > * 5. Due credit should be given to the Exolab Project > * > (http://www.exolab.org/). > * > * OF THE POSSIBILITY OF SUCH DAMAGE. > * > * Copyright 1999 (C) Exoffice Technologies Inc. All Rights Reserved. > * > Yes, this does seems like a serious problem. Can the original contributor be contacted? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
Barry Lind <barry@xythos.com> writes:
> A question came up on the jdbc mail list today that I couldn't answer.
> It involves some code that is in the jdbc cvs tree (and has been for
> many releases). This code contains the following license terms in each
> file:
> [ snip ]
> Is this a problem?
Looks like a pretty standard BSD-style license to me. I don't see a
problem.
regards, tom lane
> * > * 5. Due credit should be given to the Exolab Project > * > (http://www.exolab.org/). > * > * Copyright 1999 (C) Exoffice Technologies Inc. All Rights Reserved. > * This was the part that seemed to be a problem. Do we need to mention exolab in our COPYRIGHT announcment in psql? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
I'm not sure its a problem. The source code already contains the copyright, and this only affects the JDBC driver. Perhaps we just need to put in the JDBC driver readme file that parts were provided by Exolab? I guess, it all depends on who defines "due credit". The code was submitted by Assaf Arkin <arkin@exoffice.com>. Who gets to ask? On Wed, 2002-01-02 at 15:05, Bruce Momjian wrote: > Barry Lind wrote: > > > > A question came up on the jdbc mail list today that I couldn't answer. > > It involves some code that is in the jdbc cvs tree (and has been for > > many releases). This code contains the following license terms in each > > file: > > > > > * 5. Due credit should be given to the Exolab Project > > * > > (http://www.exolab.org/). > > * > > * OF THE POSSIBILITY OF SUCH DAMAGE. > > * > > * Copyright 1999 (C) Exoffice Technologies Inc. All Rights Reserved. > > * > > > > Yes, this does seems like a serious problem. Can the original > contributor be contacted? > > -- > Bruce Momjian | http://candle.pha.pa.us > pgman@candle.pha.pa.us | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster -- Virtually, Ned Wolpert <ned.wolpert@knowledgenet.com> D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45
Ned Wolpert wrote: Checking application/pgp-signature: FAILURE -- Start of PGP signed section. > I'm not sure its a problem. The source code already contains the > copyright, and this only affects the JDBC driver. Perhaps we just need > to put in the JDBC driver readme file that parts were provided by > Exolab? > > I guess, it all depends on who defines "due credit". The code was > submitted by Assaf Arkin <arkin@exoffice.com>. Who gets to ask? To make things even more complex, the newer BSD copyright doesn't have a "due credit" clause. See the COPYRIGHT file at the top of our source tree. I suppose the copyright at the top of the file, and perhaps in the jdbc README is enough. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026