summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Sima <ben@bsima.me>2019-02-27 09:50:56 -0800
committerBen Sima <ben@bsima.me>2019-02-27 09:50:56 -0800
commit82396144abf6d9896dd14220db64333e8a83e5b6 (patch)
tree3e22fcd98a06941880a95c772c43048cc2bbba45
parentbeac73676503ee54baad31387dd8d65c15bbc9a0 (diff)
Add developer workflow goals
-rw-r--r--README.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/README.md b/README.md
index a7a38e9..4bcc314 100644
--- a/README.md
+++ b/README.md
@@ -27,6 +27,23 @@ To get a development shell, for example to work on ibb, you can do:
[2 of 2] Compiling Ibb ( apex/Ibb.hs, interpreted )
Ok, two modules loaded.
+Goals of the developer workflow:
+
+- have minimal ceremony
+- default to asynchrony, but allow for synchronous work when necessary
+- automate the boring stuff
+- standardize environments, tooling, and versions to minimize friction while
+ collaborating
+- support the longevity and self-sustainability of the project
+
+Ideally, each contributor should be able to go off grid for a day or a week or
+more, continue working offline, submit their work when finished, and have no or
+minimal conflicts. This also refers to the resiliance of the production systems.
+
+We should never need "out of office" email auto-replies, or urgent contact. No
+pager duy, no daily standups. Yes, this policy will affect what code we write,
+not just how we write it; that is by design.
+
# Deployment
To build the production server config locally: