Project

General

Profile

Mission and Principles » History » Version 20

Tom Clegg, 04/09/2013 11:04 AM

1 19 Ward Vandewege
h1. Arvados Mission, Philosophy and Principles
2 1 Anonymous
3 2 Anonymous
h2. Mission
4 1 Anonymous
5 19 Ward Vandewege
Arvados is dedicated to enabling great medical care by enabling the large-scale analysis of biomedical data.
6 1 Anonymous
7 17 Ward Vandewege
h2. Free and Open Source Software
8 1 Anonymous
9 20 Tom Clegg
We believe our success depends on our software being free and accessible to all.
10 1 Anonymous
11 20 Tom Clegg
When we say "free", we refer to the freedoms defined by the Free Software Foundation's article, "_What is Free Software_:":http://www.gnu.org/philosophy/free-sw.html
12 1 Anonymous
13
* The freedom to run the program, for any purpose.
14
* The freedom to study how the program works and adapt it to your needs.
15
* The freedom to redistribute copies so you can help others.
16
* The freedom to improve the program and release your improvements to the public, so that everyone benefits.
17 20 Tom Clegg
18
We also adhere to the 10 core criteria of open source software defined by the "Open Source Initiative:":http://opensource.org/docs/definition.php
19 1 Anonymous
20
* Software must be free to redistribute.
21
* The program must include source code.
22
* The licence must allow people to experiment with and redistribute modifications.
23
* Users have a right to know who is responsible for the software they are using.
24
* There should be no discrimination against any person or group.
25
* The licence must not restrict anyone from making use of the program in a specific field.
26
* No-one should need to acquire an additional licence to use or redistribute the program.
27
* The licence must not be specific to a product.
28
* The licence must not restrict other software.
29
* The licence must be technology-neutral.
30
31 19 Ward Vandewege
The commitment to free and open software is manifest in how the software is licensed and developed through and open and diverse community. (Learn more about Arvados [[Licensing Terms]].)
32 1 Anonymous
33
h2. Built by an Open Community 
34
35 9 Anonymous
Open source 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. 
36 1 Anonymous
37 19 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 mailing list and IRC chat for conversations among developers and contributors, and we plan to hold regular design sessions through Google Hangout. Most decisions are made through a lazy consensus process and all processes are documented. 
38 1 Anonymous
39 11 Anonymous
We maintain an fully public source code repository in GIT through the entire development process. Contribution is merit-based and the code review, issues, backlog, and release schedules are all open and transparent. 
40 1 Anonymous
41 19 Ward Vandewege
The Arvados community is organized around six core principles: 
42 1 Anonymous
43 18 Ward Vandewege
* *Open Source* - We are committed to developing free and open source software. 
44 1 Anonymous
45 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. 
46 1 Anonymous
47 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. 
48 1 Anonymous
49 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. 
50 1 Anonymous
51 14 Anonymous
* *Merit* - Technical governance is a meritocracy. Working code wins arguments. 
52 1 Anonymous
53 17 Ward Vandewege
* *Respect* - We seek to build a respectful, collaborative community that is enjoyable to participate in and fosters healthy discussion and debate.