Changes between Version 30 and Version 31 of License

Timestamp:

Dec 30, 2019, 5:47:34 AM (4 years ago)

Author:

Peter Baumann

Comment:

—

License

@@ -11 +11 @@
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License / GNU General Public License at http://www.gnu.org/licenses/ for more details.
+GNU General Public License / GNU Lesser General Public License 
+at http://www.gnu.org/licenses/ for more details.
 }}}
 
@@ -18 +19 @@
 
 The rasdaman community code is licensed in a way to allow use of the system in virtually any-license software systems:
-   * client libraries (such as {{{libraslib.a}}}) and applications (such as {{{rasql}}}) as well as the OGC frontends (that is: the {{{petascope}}} servlet): [http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License LGPL] [http://www.gnu.org/licenses/lgpl-3.0.txt version 3]; see file COPYING.LESSER in the source tree root.
-   * Server-side executables (such as {{{rasserver}}} and {{{rasmgr}}}): [http://en.wikipedia.org/wiki/Gpl GPL] [http://www.gnu.org/licenses/gpl-3.0.txt version 3]; see file COPYING in the source tree root.
+   * [http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License LGPL] [http://www.gnu.org/licenses/lgpl-3.0.txt version 3] for the client libraries (such as {{{libraslib.a}}}) and applications (such as {{{rasql}}}) as well as the OGC frontends (aka {{{petascope}}}); see file COPYING.LESSER in the source tree root.
+   * [http://en.wikipedia.org/wiki/Gpl GPL] [http://www.gnu.org/licenses/gpl-3.0.txt version 3] for server-side executables (such as {{{rasserver}}} and {{{rasmgr}}}); see file COPYING in the source tree root.
 
-See the standard header in each file in the source tree to determine its respective license scheme.
+Check the standard header in each file in the source tree to determine its respective license scheme.
 
 '''Why This Dual Scheme?''' In short: For maximizing both free use and community return. We chose GPL for the server because
    * Life is a give and take, and we believe that open-source is about sharing by and among all those who benefit.
-   * A [http://www.rasdaman.com commercially supported, non-GPL-restricted variant of rasdaman] is available which we recommend to all users who have requirements that go beyond GPL. Please [http://rasdaman.com/index.php#imprint contact the company] for more details about the commercial version.
-
-
-On the other hand, rasdaman can be used embedded in other systems as well: the LGPL client connectors allow for an uninhibited inclusion (such as linking) of the rasdaman client libraries with code of any licensing model, including proprietary, aslong as LGPL regulations are adhered to.
+   * A [http://www.rasdaman.com commercially supported, non-GPL-restricted variant of rasdaman] is available which we recommend to all users who have requirements that go beyond GPL. Please [http://rasdaman.com/index.php#imprint contact the company] for details.
+   * rasdaman can be used embedded in other systems as well: the LGPL client connectors allow for an uninhibited inclusion (such as linking) of the rasdaman client libraries with code of any licensing model, including proprietary, as long as LGPL regulations are adhered to.
 
 '''Why do code suppliers have to accept the [wiki:ContributorAgreement Rasdaman Contribution Agreement]?''' Because we need to maintain a strict code provenance in order to allow us to rightfully make this code available under the conditions stated above. In other words: should there be some code which conflicts with the GPL / LGPL regulations we claim then you, as a user of rasdaman, would run the risk of possibly getting "infected" by incompatible licenses. Organizations like [http://www.osgeo.org/ Open Source Geo Foundation, OSGeo] check this for open-source projects, and we indeed are undergoing a detailed provenance review (on single file granularity!) during [http://wiki.osgeo.org/wiki/Rasdaman_Incubation_Status rasdaman's OSGeo incubation].