summaryrefslogtreecommitdiff
path: root/iterations/20190601-to-20190615.mdwn
blob: 407bdb9d0bbd9502aa07f485d8b66250577f4509 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
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`