Difference between revisions of "Team"
Jump to navigation
Jump to search
m (→The Agreement) |
|||
| Line 5: | Line 5: | ||
* 67P is sorely needed an we want to use it today/asap/yesterday | * 67P is sorely needed an we want to use it today/asap/yesterday | ||
* We can imagine this to be commercially successful, and we can see us founding a company for the paid/pro version and potentially working for it at some point (to whatever degree that might be) | * We can imagine this to be commercially successful, and we can see us founding a company for the paid/pro version and potentially working for it at some point (to whatever degree that might be) | ||
| − | * We will take the first step and implement the [[prototype]] MVP as a side project. Most of us will come to | + | * We will take the first step and implement the [[prototype]] MVP as a side project. Most of us will come to [Chaos Camp] in August 2015, so we'll try to finish the MVP during our time there and then define how to proceed |
* All work done until then, and (as far as possible) forever, will be published under open-source licenses. However, we want to protect the project name/ trademark, so that people using the name/trademark commercially need to ask our permission, and so that we can use the name commercially ourselves for the benefit of all contributors (incl. non-partners/employees/shareholders). | * All work done until then, and (as far as possible) forever, will be published under open-source licenses. However, we want to protect the project name/ trademark, so that people using the name/trademark commercially need to ask our permission, and so that we can use the name commercially ourselves for the benefit of all contributors (incl. non-partners/employees/shareholders). | ||
Revision as of 15:40, 23 March 2015
The Agreement
The core team consists of a group of people, who have agreed with each other on several things:
- 67P is sorely needed an we want to use it today/asap/yesterday
- We can imagine this to be commercially successful, and we can see us founding a company for the paid/pro version and potentially working for it at some point (to whatever degree that might be)
- We will take the first step and implement the prototype MVP as a side project. Most of us will come to [Chaos Camp] in August 2015, so we'll try to finish the MVP during our time there and then define how to proceed
- All work done until then, and (as far as possible) forever, will be published under open-source licenses. However, we want to protect the project name/ trademark, so that people using the name/trademark commercially need to ask our permission, and so that we can use the name commercially ourselves for the benefit of all contributors (incl. non-partners/employees/shareholders).
The Team
| Name | a.k.a. | Involvement/expertise |
|---|---|---|
| Ben Kero | bkero | SysOps, DevOps, *nix systems, infrastructure development, IRC, open-source collab/community/dev/relations, ... |
| David Grieshammer | lsa, lsa232 | User experience design, interaction design, graphic/web design, audio, ... |
| Garret Alfert | galfert | Software development (full-stack), Ember.js, RemoteStorage, back-end, payments, ... |
| Grégory Karékinian | gregkare, gkarekinian | Infrastructure development, DevOps, operations, Chef, Ruby, *nix systems ... |
| Jan Lelis | janlelis, jan, jaaan | Software development (full-stack), WebRTC, Ruby, Rails, JavaScript, AngularJS |
| Michael Bumann | bumi, derbumi | Fin-tech development, blockchain technologies, Bitcoin, Ruby, Java, JavaScript, crowd funding/investment, ... |
| Nick Jennings | silverbucket, slvrbckt | Software development (full-stack), JavaScript, Node.js, Sockethub, RemoteStorage, ... |
| Sebastian Kippe | basti, skddc, raucao | Software development (full-stack), front-end/UI, Ember.js, RemoteStorage / business, funding, human resources, ... |
