bigchaindb
/
bigchaindb
mirror of https://github.com/bigchaindb/bigchaindb.git
1
0
Fork 0
Code Releases Activity
bigchaindb/LICENSES.md

25 lines
1.9 KiB
Markdown
Raw Normal View History

Added LICENSES.md (open source / open content)
2016-02-08 13:03:30 +01:00
# Code Licenses
More revisions to the LICENSES.md file Expanded explanation of the licensing options.
2016-09-02 10:17:09 +02:00
For all code in this repository, BigchainDB GmbH ("We") either:
Added LICENSES.md (open source / open content)
2016-02-08 13:03:30 +01:00
More revisions to the LICENSES.md file Expanded explanation of the licensing options.
2016-09-02 10:17:09 +02:00
1. owns the copyright, or
2. owns the right to sublicense it (because all external contributors must agree to a Contributor License Agreement).
[WIP]: Move the bigchaindb/nginx_3scale repo under bigchaindb/bigchaindb - All files moved to k8s/nginx-3scale with directory structure consistent with k8s/nginx-http(s) - Top level LICENCES.md updated - Renaming entry point script to nginx_openresty_entrypoint.bash
2017-08-16 14:04:43 +02:00
3. The licensing of things in the k8s/nginx-openresty/ directory is described by a separate LICENSE.md file in that directory.
Added note to LICENSES.txt Added a note: "If you want to make modifications to the code in _this_ repository and you want to keep those modifications proprietary, then you must get a commercial license from BigchainDB GmbH."
2016-08-21 18:50:59 +02:00
More revisions to the LICENSES.md file Expanded explanation of the licensing options.
2016-09-02 10:17:09 +02:00
Therefore We can choose how to license all the code in this repository. We can license it to Joe Xname under one license and Company Yname under a different license.
The two general options are:
1. You can get it under a commercial license for a fee. We can negotiate the terms of that license. It's not like we have some standard take-it-or-leave it commercial license. If you want to modify it and keep your modifications private, then that's certainly possible. Just ask.
2. You can get it under the AGPLv3 license for free. You don't even have to ask us. That's because all code in _this_ repository is licensed under the GNU Affero General Public License version 3 (AGPLv3), the full text of which can be found at [http://www.gnu.org/licenses/agpl.html](http://www.gnu.org/licenses/agpl.html).
If you don't like the AGPL license, then just ignore it. It doesn't affect any other license.
All short code snippets embedded in the official BigchainDB _documentation_ are also licensed under the Apache License, Version 2.0, the full text of which can be found at [http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0).
Added LICENSES.md (open source / open content)
2016-02-08 13:03:30 +01:00
Updated LICENSES.md (#570) The main change we made was to move the responsibility of stating code licenses to the respective repositories.
2016-08-17 17:52:51 +02:00
For the licenses on all other BigchainDB-related code, see the LICENSE file in the associated repository.
Added LICENSES.md (open source / open content)
2016-02-08 13:03:30 +01:00
# Documentation Licenses
The official BigchainDB documentation, _except for the short code snippets embedded within it_, is licensed under a Creative Commons Attribution-ShareAlike 4.0 International license, the full text of which can be found at [http://creativecommons.org/licenses/by-sa/4.0/legalcode](http://creativecommons.org/licenses/by-sa/4.0/legalcode).