Mission and Principles » History » Version 27

Jonathan Sheffi, 08/05/2015 05:09 PM

1 21 Tom Clegg
h1. Arvados Mission and Principles
2 1 Anonymous
3 2 Anonymous
h2. Mission
4 1 Anonymous
5 26 Anonymous
Arvados is dedicated to enabling great medical care through the large-scale analysis of biomedical data.
6 1 Anonymous
7 22 Ward Vandewege
h2. Free software
8 1 Anonymous
9 22 Ward Vandewege
We believe our success depends on Arvados being free software.
10 1 Anonymous
11 25 Ward Vandewege
"Free software" means software that respects users' freedom and community, as defined in the "Free Software Definition":http://www.gnu.org/philosophy/free-sw.html by the Free Software Foundation.
12 1 Anonymous
13 25 Ward Vandewege
Software freedom is defined by the four freedoms laid out in the Free Software Definition:
14 22 Ward Vandewege
15 1 Anonymous
* The freedom to run the program, for any purpose.
16 1 Anonymous
* The freedom to study how the program works and adapt it to your needs.
17 1 Anonymous
* The freedom to redistribute copies so you can help others.
18 1 Anonymous
* The freedom to improve the program and release your improvements to the public, so that everyone benefits.
19 1 Anonymous
20 22 Ward Vandewege
These freedoms imply that the software is open source.
21 1 Anonymous
22 22 Ward Vandewege
Our commitment to free software is manifest in how the software is [[Licensing Terms|licensed]] and developed.
23 1 Anonymous
24 23 Ward Vandewege
h2. Built by a Community 
25 1 Anonymous
26 23 Ward Vandewege
Free software unlocks the potential of community to collaborate and develop in a decentralized way where the collective effort produces something greater than any individual or single company could achieve on their own. This is especially important in healthcare where the innovation has the potential to directly affect the health and well being of billions of people. 
27 1 Anonymous
28 24 Ward Vandewege
The Arvados design process is open and transparent. The project uses best-practices from agile development methodologies. A public backlog represents the work that is planned. There is a [[IRC and Mailing Lists|mailing list and IRC channel]] for conversations among developers and contributors, and we hold regular design sessions through Google Hangout. Most decisions are made through a lazy consensus process and all processes are documented. 
29 1 Anonymous
30 21 Tom Clegg
We maintain an fully public source code repository through the entire development process. Contribution is merit-based and the code review, issues, backlog, and release schedules are all open and transparent. 
31 1 Anonymous
32 19 Ward Vandewege
The Arvados community is organized around six core principles: 
33 1 Anonymous
34 18 Ward Vandewege
* *Open Source* - We are committed to developing free and open source software. 
35 1 Anonymous
36 14 Anonymous
* *Elegance* - We aim to create software that is well designed, flexible, modular, extensible and easily maintainable. We strive for user experiences that are thoughtful, simple and easy-to-use. 
37 1 Anonymous
38 14 Anonymous
* *Transparency* - All discussions and decisions happen in open forums. The community controls the design process. All decisions, processes, and discussions are documented and preserved in the project website. 
39 1 Anonymous
40 19 Ward Vandewege
* *Quality* - We strive to create highly-quality code that is reliable, secure, scalable, tested, documented and maintainable. We understand that Arvados powers mission-critical systems. 
41 1 Anonymous
42 14 Anonymous
* *Merit* - Technical governance is a meritocracy. Working code wins arguments. 
43 1 Anonymous
44 1 Anonymous
* *Respect* - We seek to build a respectful, collaborative community that is enjoyable to participate in and fosters healthy discussion and debate.
45 26 Anonymous
46 26 Anonymous
h2. Supported Commercially
47 26 Anonymous
48 26 Anonymous
The Arvados project was started with the assumption that for-profit companies and service providers will come to support Arvados commercially while still maintaining a deep commitment to open source and the Arvados community. We believe this is part of what is necessary to make the project successful in the real-world. When IT organizations deploy major Arvados implementations, many of them will look to commercial vendors for design, implementation, and support services. We think this is a great thing, and it's consistent with what has happened for many of the most successful open source projects. We also hope to see commercial vendors building applications and services on-top of an integrated with Arvados. 
49 26 Anonymous
50 26 Anonymous
By combining an AGPL license for the core code, which helps to protect the whole community and an Apache 2 license for the SDKs, we believe we have a configuration where we can maintain a strong and vibrant open source project that doesn't become fragmented, at the same time that we enable proprietary and commercial innovation on top of and adjacent to the Arvados platform.
51 27 Jonathan Sheffi
52 27 Jonathan Sheffi
To read a more detailed summary of the Arvados license choices and their implications, read the [[Arvados Licenses FAQ]].