Changes between Version 17 and Version 18 of SWLicense


Ignore:
Timestamp:
03/27/2009 07:59:28 PM (10 years ago)
Author:
RayPlante
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SWLicense

    v17 v18  
    8484 
    8585  * Statement Identifying Licensor and Authors 
    86  
    8786{{{ 
    8887LSST Data Management System Software 
     
    102101  * University of Arizona, Steward Observatory 
    103102  * University of California Davis 
    104   * The San Diego Supercomputing Center (SDSC) at the University of California San Diego 
     103  * The San Diego Supercomputing Center (SDSC) at the University of California  
     104    San Diego 
    105105  * University of Washington 
     106 
     107Use and redistribution of this software is covered by the GNU Public License Version 3  
     108(GPLv3) or later, as detailed below.  A copy of the GPLv3 is also available at  
     109<http://www.gnu.org/licenses/>. 
     110 
     111========================================================================================== 
    106112}}} 
    107113   '''Notes:''' 
    108         *  Individual author names ''may'' be provided else where in the file as appropriate (e.g. as part of Doxygen API documentation markup 
     114        *  Individual author names ''may'' be provided else where in the file as appropriate (e.g. as part of Doxygen API documentation markup). 
    109115        *  Additional institutions may be added to the credit list over time as contributions are made 
    110116        *  No effort will be made to update this list for packages that have already been released 
    111117        *  For ease of maintenance, no effort will be made to remove institutions from the credit list even when the particular package distribution contains no actual contributions from that institution.  
    112118 
     119  * The [http://www.gnu.org/licenses/gpl.txt GNU v3 License text] 
     120     * when there are allowable exceptions to be made (e.g. [http://www.fsf.org/licensing/licenses/gpl-faq.html#LinkingOverControlledInterface linking with proprietary software through well-defined interfaces]), these will be added after this text. 
     121 
     122  * For each 3rd-party software product that is part of the software's run-time (e.g. excluding doxygen), we include a reference to the software's license as required by that license.  For example: 
     123{{{ 
     124This software makes use Numpy, Copyright (c) 2005, NumPy Developers 
     125All rights reserved. 
     126 
     127Redistribution and use in source and binary forms, with or without 
     128modification, are permitted provided that the following conditions are 
     129met: 
     130 
     131    * Redistributions of source code must retain the above copyright 
     132       notice, this list of conditions and the following disclaimer. 
     133 
     134    * Redistributions in binary form must reproduce the above 
     135       copyright notice, this list of conditions and the following 
     136       disclaimer in the documentation and/or other materials provided 
     137       with the distribution. 
     138 
     139    * Neither the name of the NumPy Developers nor the names of any 
     140       contributors may be used to endorse or promote products derived 
     141       from this software without specific prior written permission. 
     142 
     143THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 
     144"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
     145LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 
     146A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 
     147OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 
     148SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
     149LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
     150DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 
     151THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
     152(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 
     153OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 
     154 
     155============================================================================= 
     156}}} 
     157 
    113158 
    114159== History == 
    115160 
    116 The development of this Open Source License policy can be found previous versions of this document; see in particular: version 15.   
    117  
    118  
    119 == CCB Discussion: Four Alternatives == 
    120  
    121 This proposal was discussed on 3 Sept. and the GPL compatibility issue continues to nag at us.  We identified four alternative proposals: 
    122  
    123   1.  Apache 2 + GPL 
    124          We adopt the [http://www.opensource.org/licenses/apache2.0.php Apache 2 License] for our LSST source code.  Assuming we link against GPLed libraries, our binary distributions will be distributed under GPL, as required by the GPLed libraries. 
    125          *  Apache 2 has the advantage in that it will allow other people link our libraries to non-open source code.  This, of course, would have to be limited to LSST code that itself does not link against GPL.   
    126          *  Technically, using Apache 2 does not allow us to link against GPLv2 licensed libraries; thus, this option requires that we ignore this fact.  Given that GPLv3 addresses this incompatibility issue, ignoring this issue is not likely to result in an enforcement action.  See [http://www.oss-watch.ac.uk/resources/apache2.xml#body.1_div.3 this discussion from OSS watch] for details. 
    127   2.  Mod-BSD + GPL 
    128          We adopt the [http://www.opensource.org/licenses/bsd-license.php Modified BSD Licence] for our LSST source code.  Assuming we link against GPLed libraries, our binary distributions will be distributed under GPL, as required by the GPLed libraries. 
    129          *  Like Apache 2, this has the advantage that it will allow other people link our libraries to non-open source code.  This, of course, would have to be limited to LSST code that itself does not link against GPL.  
    130          *  This license is compatible with GPL (mainly by saying less) 
    131   3.  public domain + GPL 
    132          We do not license our LSST software; we simply put it into the public domain.  Assuming we link against GPLed libraries, our binary distributions will be distributed under GPL, as required by the GPLed libraries. 
    133          *  This option is explicitly allowed by the GPL.   
    134   4.  GPL  
    135          We adopt GPL v3 for our LSST software.  All distributions, source and binary have the same license.   
    136          *  This option is explicitly allowed by the GPL; there are no legal uncertainties in this option 
    137          *  In exchange for the simplicity of our distributions, it will not be possible for other people to link our libraries with non-open source code.   
     161The development of this Open Source License policy can be found previous versions of this document; see in particular: [http://dev.lsstcorp.org/trac/wiki/SWLicense?version=15 version 15].  The original proposal to the TCT, developed in roughly August 2008 by Francesco Pierfederici, was to use the Apache 2 License to allow commercial use of the software.  This raised questions concerning the combination and redistribution of our code with other GPLed software.  Four alternatives were then put on the table for discussion:  
     162   1. Apache 2 plus GPL for combined binary distributions 
     163   2. Modified BSD plus GPL for combined binary distributions 
     164   3. Public Domain plus GPL for combined binary distributions 
     165   4. Pure GPL Licensing 
     166Choice 4 was chosen because it offer the least legal ambiguity.  This meant that commercialization could not be supported.   
    138167 
    139168