summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Sima <ben@bsima.me>2019-11-19 10:33:49 -0800
committerBen Sima <ben@bsima.me>2019-11-19 10:33:49 -0800
commit1cdd122a07b28157d136a2cbf07a97117e6ac605 (patch)
tree31875ae4ac3def46e43b64bf669a9dd7db26b111
parentc2a556abd8c7d39fbbe333b514217b1e621048cb (diff)
Update README
-rw-r--r--README.md18
1 files changed, 8 insertions, 10 deletions
diff --git a/README.md b/README.md
index 12e3667..6a458fb 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
The source tree maps to the DNS namespace that we own. The purpose of
this mapping is to keep things organized hierarchically in how they are
deployed on the Internet. The main 'common' space is `Com.Simatime`,
-other namespaces should be related to the application.
+other namespaces should be related to their application.
Development aspects should be localized to their sub-namespaces as much
as possible. Only after sufficient iteration such that interfaces are
@@ -37,7 +37,8 @@ And to deploy:
These three common tasks are captured in the `./bild`, `./ghci`, and
`./push` scripts.
-There's also a `./rise` script which builds and runs an app. I use it like:
+There's also a prototype `./rise` script which builds and runs an app. I
+use it like:
ag -l | entr -r ./rise Com.InfluencedByBooks
@@ -59,12 +60,9 @@ We should never need "out of office" email auto-replies, or urgent
contact. No pager duty, no daily stand-ups. Yes, this policy will affect
what code we write, not just how we write it; that is by design.
-TODO:
+TODO: document how we use the following:
-## Org
-
-## Git
-
-## Email
-
-## IRC
+- Org
+- Git
+- Email
+- IRC