Arvados Licenses FAQ » History » Version 6

Ward Vandewege, 10/03/2018 06:00 PM

1 6 Ward Vandewege
h1. Arvados Licensing FAQ
2 1 Jonathan Sheffi
3 1 Jonathan Sheffi
This FAQ is designed to answer questions about licensing for the Arvados open source project.
4 1 Jonathan Sheffi
5 1 Jonathan Sheffi
{{toc}}
6 1 Jonathan Sheffi
7 6 Ward Vandewege
h2. Software licenses
8 1 Jonathan Sheffi
9 5 Ward Vandewege
The Arvados API server and the core Arvados system services, Keep and Crunch, are distributed under the "AGPLv3 license":http://www.gnu.org/licenses/agpl-3.0.en.html. Workbench, a browser-based visual tool that calls the Arvados APIs, is distributed under the "AGPLv3 license":http://www.gnu.org/licenses/agpl-3.0.en.html. The "Software Development Kits (SDKs)":http://doc.arvados.org/sdk/index.html, the code samples in the "Arvados documentation":http://doc.arvados.org/, and the "tools for writing Crunch scripts":http://doc.arvados.org/user/topics/crunch-tools-overview.html, are distributed under the "Apache 2 license":http://www.apache.org/licenses/LICENSE-2.0. For more details on the licensing of each file in the codebase, see the "COPYING file":https://github.com/curoverse/arvados/blob/master/COPYING.
10 1 Jonathan Sheffi
11 1 Jonathan Sheffi
The Arvados documentation is licensed under the "Creative Commons Attribution-Share Alike 3.0 United States license":https://creativecommons.org/licenses/by-sa/3.0/us/.
12 1 Jonathan Sheffi
13 1 Jonathan Sheffi
h2. Why were these licenses chosen?
14 1 Jonathan Sheffi
15 1 Jonathan Sheffi
Arvados has several design goals. The OSS licenses were chosen to specifically support three of them:
16 1 Jonathan Sheffi
17 1 Jonathan Sheffi
*Open Standards*: With Arvados, we hope to create an industry standard around which data scientists can coalesce and organize. We believe that this is only possible when developing such a standard in the open and while listening to the needs and wants of the industry. The AGPLv3 license for the core stack prevents an industry stakeholder from attempting to move the stack in favor of a particular vendor.
18 1 Jonathan Sheffi
19 4 Jonathan Sheffi
*Federation*: Federation is the ability to author a pipeline in one Arvados deployment and run it in any other Arvados deployment, whether that deployment is on an on-premise cluster or on a public cloud provider. To do so requires a uniform set of APIs and environments, and fragmentation of the Arvados core code base increases the risk that an analysis will break for no reason other than that the two installations came from a fork in the code base. Licensing the core stack under the AGPLv3 drastically limits the opportunity for fragmentation of the code base, preserving federation capabilities for everyone who deploys Arvados.
20 1 Jonathan Sheffi
21 2 Anonymous
*Flexible Authoring*: Arvados was always intended to be used by authors of both open source and proprietary analyses, pipelines, tools, and applications. Therefore, the SDKs and code samples are distributed under the Apache 2 license, which allow authors to develop open source or proprietary solutions on top of Arvados.
22 1 Jonathan Sheffi
23 1 Jonathan Sheffi
h2. What are the implications of these licenses for my own code?
24 1 Jonathan Sheffi
25 1 Jonathan Sheffi
According to the AGPLv3 license, all contributions to and modifications of the core Arvados code base that are distributed, or made available for use over a network, must themselves be available to recipients under the same license. This ensures that all those who deploy Arvados are entitled to the same improvements in underlying infrastructure, and that the core of Arvados does not fragment.
26 1 Jonathan Sheffi
27 1 Jonathan Sheffi
According to the Apache 2 license, derivative works are not required to be redistributed under any license. Therefore, developers can choose to build proprietary pipelines and client software for Arvados, and those works are protected under international copyright law.
28 1 Jonathan Sheffi
29 1 Jonathan Sheffi
MongoDB’s licensing also follows this paradigm, and it is summarized in "their blog on the same topic":http://blog.mongodb.org/post/103832439/the-agpl.