summaryrefslogtreecommitdiff
path: root/iterations/20190601-to-20190615.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'iterations/20190601-to-20190615.mdwn')
-rw-r--r--iterations/20190601-to-20190615.mdwn46
1 files changed, 46 insertions, 0 deletions
diff --git a/iterations/20190601-to-20190615.mdwn b/iterations/20190601-to-20190615.mdwn
new file mode 100644
index 0000000..407bdb9
--- /dev/null
+++ b/iterations/20190601-to-20190615.mdwn
@@ -0,0 +1,46 @@
+[[!meta title="1st to 15th June 2019"]]
+[[!meta author="Daniel Silverstone"]]
+[[!meta date="2019-06-01 18:00:00 +0100"]]
+
+Present
+=======
+
+* Lars Wirzenius
+* Daniel Silverstone
+
+Notes
+=====
+
+During this iteration discussion we covered where we were up to, went over the
+formatting of the `fable-poc` doc generator, planned out roughly the timeline
+of what we need for being able to present at the BBQ, and reconfirmed our
+intent to be able to present `fable` in some more concrete form at the Debian
+mini-conf in Cambridge in November.
+
+Retrospective
+=============
+
+We didn't have concrete actions leading into this discussion.
+
+Iteration plan
+==============
+
+Lars
+----
+
+1. Migrate the PoC codegen into `fable-poc` and ensure it is capable of
+ generating basic tests.
+2. Write a fable document with scenarios, bindings, functions, etc. to actually
+ test something.
+3. Initial outline of the tutorial
+
+Daniel
+------
+
+Produce a Rust PoC capable of:
+
+1. Reading markdown files
+2. Identifying and extracting Fable scenarions from those files
+3. Writing out markdown files containing the above.
+
+Said PoC will be in the `fable-poc` repository in a directory called `rust-poc`