2017-09-15 21:21:26 +00:00
|
|
|
---
|
2017-09-16 15:46:56 +00:00
|
|
|
title: The concept and team
|
2017-09-15 21:21:26 +00:00
|
|
|
author: someone
|
|
|
|
|
abstract: some abstract
|
|
|
|
|
---
|
|
|
|
|
|
2017-09-16 15:46:56 +00:00
|
|
|
# Mission
|
2017-09-15 21:21:26 +00:00
|
|
|
|
2017-09-16 15:46:56 +00:00
|
|
|
The goal of robur is to develop robust digital infrastructure. This goal is
|
|
|
|
|
achieved by continuous maintainence of permissively licensed (MIT/ISC/BSD) open
|
|
|
|
|
source libraries, which are used by various partners and supporters.
|
|
|
|
|
|
|
|
|
|
Robur is a non-profit endeavour, the ultimate goal is not to earn as much as
|
|
|
|
|
possible, but instead to enable more people to run their own digital
|
|
|
|
|
infrastructure. Minimising the executable size of services and cutting down
|
|
|
|
|
complexity is crucial to help people to understand the technology.
|
|
|
|
|
|
|
|
|
|
Rewards (in terms of shirts, money, stickers, retreat attendance) will be given
|
|
|
|
|
to contributors from the open source community.
|
|
|
|
|
|
|
|
|
|
Experience in developing and deploying the technology itself will be reflected
|
|
|
|
|
on in academic papers, and talks at workshops and conferences.
|
|
|
|
|
|
|
|
|
|
Transparency is another goal of robur, the annual balance will be accessible to
|
|
|
|
|
the public.
|
|
|
|
|
|
|
|
|
|
# Non-profit company
|
|
|
|
|
|
|
|
|
|
Supporters can make charitable donations to robur, which will be used for
|
|
|
|
|
further development and maintainence of software and community infrastructure.
|
|
|
|
|
|
|
|
|
|
Partners can contract robur to develop prototypes (see example
|
|
|
|
|
[projects](/Projects)). Developed libraries will be open sourced, and are
|
|
|
|
|
reusable by other interested parties. The application code itself will be
|
|
|
|
|
exclusively copyrighted by the partner. Some terms are negotiable, e.g.
|
|
|
|
|
whether the library code will be exclusively licensed to the partner for some
|
|
|
|
|
time (maximum 6 months), influence on the development roadmap, service level
|
|
|
|
|
agreements (on-call debugging, running infrastructure).
|
|
|
|
|
|
|
|
|
|
# Team
|
|
|
|
|
|
|
|
|
|
## Alfred
|
|
|
|
|
|
|
|
|
|
Alfred is a hacker. He enjoys to write code since more than 15 years, but also
|
|
|
|
|
travelling and repairing his recumbent bicycle, and being a barista.
|
|
|
|
|
|
|
|
|
|
In 2013, Alfred did his PhD in computer science about formal verification of
|
|
|
|
|
imperative code (using a higher-order separation logic and the theorem prover
|
|
|
|
|
Coq). At the moment he is busy with reanimating an executable formal model of
|
|
|
|
|
TCP/IP which can act as a test validator.
|
|
|
|
|
|
|
|
|
|
Alfred co-authored a TLS implementation from the grounds up in OCaml.
|
