summaryrefslogtreecommitdiffstats
path: root/docs/project.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/project.md')
-rw-r--r--docs/project.md11
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/project.md b/docs/project.md
index 36980d13..4d942c90 100644
--- a/docs/project.md
+++ b/docs/project.md
@@ -1,3 +1,10 @@
1# Why?
2This project started with the aim to produce a product that doesn't cater to all usecases, but does what it does well.
3We want a codebase that is well maintainable by a small team, and that can move fast.
4We want a codebase where it is fast and easy to prototype new features and turn them eventually into full implementations, without compromising the quality of the rest of the system. Additionaly the product should be portable accross a variety of platforms, including mobile, not only due to a portable codebase, but also due to different interfaces for the various formfactors.
5
6Because no existing codebase fullfills those premises or easily allows to reach them, this project started.
7
1# Vision 8# Vision
2Kontact Quick aims to be an enterprise-ready PIM solution, that has a high-quality and rock solid core. The focus of the core is on high-quality code, maintainability, stability and performance. 9Kontact Quick aims to be an enterprise-ready PIM solution, that has a high-quality and rock solid core. The focus of the core is on high-quality code, maintainability, stability and performance.
3 10
@@ -9,7 +16,7 @@ Experimental or advanced features are supported as optional addons, to not affec
9Kontact Quick aims to be available on various form-factors and platforms. 16Kontact Quick aims to be available on various form-factors and platforms.
10 17
11# Project Structure 18# Project Structure
12While this is an open project that welcomes participation from everyone who's interested, we do have an explicit team strucuture to ensure it's clear to everyone who's repsonsible for what. External contributions are alwas welcome and the team is of course open for extension. 19While this is an open project that welcomes participation from everyone who's interested, we do have an explicit team strucuture to ensure it's clear to everyone who's repsonsible for what. External contributions are always welcome and the team is of course open for extension.
13 20
14Team Lead/Maintainer: Christian Mollekopf 21Team Lead/Maintainer: Christian Mollekopf
15Team Members: Michael Bohlender, Sandro Knauss, Aaron Seigo 22Team Members: Michael Bohlender, Sandro Knauss, Aaron Seigo
@@ -17,7 +24,7 @@ Team Members: Michael Bohlender, Sandro Knauss, Aaron Seigo
17It's the team leads responsibility to: 24It's the team leads responsibility to:
18 25
19* Organize regular online meetings (medium yet unknown) 26* Organize regular online meetings (medium yet unknown)
20* Give direction to the product and ensure it's followed. 27* Give direction to the product and ensure it's followed
21* Direct development and oversee decisions 28* Direct development and oversee decisions
22* Ensure documentation of decisions 29* Ensure documentation of decisions
23 30