From 63fe7b0d673e3a57e8b3f7debba26c5882ea6868 Mon Sep 17 00:00:00 2001 From: Hannes Mehnert Date: Sat, 16 Sep 2017 18:44:02 +0100 Subject: [PATCH] reword --- About | 38 +++++++++++++++++++------------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/About b/About index 6d664ca..79be7eb 100644 --- a/About +++ b/About @@ -14,14 +14,12 @@ Robur is a non-profit endeavour that strives to enable more people to run their 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. +Rewards (in terms of shirts, money, stickers, hardware, retreats) for +contributors of the open source community are part of the funding plan. +Academic papers and talks at workshops and technical conferences will be +written to document the development and deployment of the technology. +The annual balance will be opened for the public to satisfy transparency what +donations and funding is used for. ## Non-profit company @@ -29,23 +27,26 @@ 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 are open sourced if possible, to be -reusable by other interested parties. The application code itself is -exclusively copyrighted by the partner. Terms are negotiable, e.g. -whether the library code will be exclusively licensed to the partner for some -time, influence on the development roadmap, service level -agreements (on-call debugging, running infrastructure). +[projects](/Projects)). Developed libraries will be open sourced under a +permissive license, and thus can be used by others. The code for the +application itself will be owned by the partner. Examples include branding, +configuration and composition of libraries. + +Negotiable terms include time-limited exclusively licenses, service level +agreements (on-call troubleshooting, running infrastructure, updates), early +access on new development, influencing on the development roadmap. ## 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. +Alfred is a research associate at University of Cambridge. He enjoys to write +code, and also travelling and repairing his recumbent bicycle, and being a +barista. -In 2013, Alfred did his PhD in computer science about formal verification of +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 +Coq). At the moment he is working on 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. @@ -63,4 +64,3 @@ Her Erdős number is 4. ## Contact If you want to get in contact with us, write an email to us AT robur DOT io. -