Changes between Version 16 and Version 17 of License


Ignore:
Timestamp:
Jan 20, 2012, 12:44:27 PM (13 years ago)
Author:
Peter Baumann
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • License

    v16 v17  
    1717On 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.
    1818
    19 '''Why do code suppliers have to accep the 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].
     19'''Why do code suppliers have to accep 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].
    2020
    2121