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
61
62
63
|
[[!meta title=" 13th to 27th July 2019"]]
[[!meta author="Lars Wirzenius"]]
[[!meta date="2019-07-13 20:00:00 +0300"]]
Present
=======
* Lars Wirzenius
* Daniel Silverstone
Notes
=====
Daniel has looked into Rust Markdown parsers. The comrak one seems
like the best choice at the moment, as it makes a round-trip easy
(parse, then re-generate input from the AST). He's also provided
review for Lars's invitation drafts.
Lars added links to the Fable tutorial and architecture document to
the front page of the Fable website, and changed typesetting of
keywords and regexp captures of scenario steps. He sent invitations to
four people to look at Fable and give us feedback. One has responded,
but we feel we need some more information from them.
Lars got stuck with writing scenarios for Fable itself, due to how
ugly embedded a scenario (or YAML) in a scenario ends up being in the
rendered document. We discussed this, and came up with an idea where
the file that would be embedded is put in a separate fenced code
block, and extracted by the code generator.
Lars ran out of time drafting a proposal for copyright licensing of
Fable, but the consensus from the previous meeting stands.
We discussed the [[roadmap]] and agreed on updating it. The website is
basically finished for the launch. (There's much possible improvement,
but it can wait until launch.)
We're still feeling good about launching in August.
Iteration plan
==============
Lars
----
1. Respond to the person who reviewed Fable, and suggest a video chat
to discuss in more detail.
1. Ponder whom else we can approach for feedback. Discuss, and invite
them to try Fable.
1. Prototype a way to have code generator extract test files from
fenced code blocks.
1. Write some preliminary scenarios for the architecture document.
1. Draft a proposal for Fable licensing for the production version,
and send to Daniel for review.
Daniel
------
1. Ponder whom else we can approach for feedback. Discuss, and invite
them to try Fable.
1. Continue work on parsing and generating Markdown in Rust.
1. Review drafts from Lars.
|
