summaryrefslogtreecommitdiff
path: root/iterations/20190727-to-20190810.mdwn
blob: 5040c0b80886108c8c719f1921abc040dbd9323a (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
47
48
49
50
51
52
53
54
55
56
57
58
59
60
[[!meta title="27th July to 10th August 2019"]]
[[!meta author="Lars Wirzenius"]]
[[!meta date="2019-07-31 10:00:00 +0300"]]

Present
=======

* Lars Wirzenius
* Daniel Silverstone

Notes
=====

Daniel has looked further into Rust Markdown parsers. There's still
some rough corners to deal with. Bascially, we want full support for
the Markdown flavours we will use, and also support for producing good
error message for the user. This will require being able to tell, in
the error message, in which source file and location the error
happened.

Lars wrote up a concrete proposal for licensing, based on earlier
consensus, and Daniel approved it. It has been added to the Fable
website (<https://fable.liw.fi/license/>).

We had a video chat with someone who reviewed Fable and this helped us
clarify the way to talk about Fable. Lars updated the architecture
document to add a section on motivation for Fable.

We approached a few other people as well, for feedback on Fable.

Lars nailed down a concrete syntax proposal for dealing with test data
for scenarios, based on earlier suggestion by Daniel. It's not been
implemented yet, but it's clearly implementable and it'll do for the
launch. This unblocks us from making a few more scenarios for Fable
itself.

We discussed how we'll do the actual launch at the August BBQ party.
Daniel will bring a laptop we can let people use, and on which we can
optionally record their session (if they permit us), for later
analysis. We added a node to the roadmap to prepare and bring the
laptop.

Iteration plan
==============

Lars
----

1. Write some preliminary scenarios for the architecture document.
1. Chat with a friend about Fable.
1. Chat with a colleague, with testing experience, about Fable.
1. Look at ways to do definition lists in Markdown.
1. Review and ponder on Fable marketing.

Daniel
------

1. Continue work on parsing and generating Markdown in Rust.
1. Talk with another hobby project of his about Fable.
1. Review and ponder on Fable marketing.