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
64
65
66
67
68
69
70
71
72
73
74
75
|
[[!meta title="15th to 29th June 2019"]]
[[!meta author="Lars Wirzenius"]]
[[!meta date="2019-06-15 20:00:00 +0300"]]
Present
=======
* Lars Wirzenius
* Daniel Silverstone
Notes
=====
During this iteration discussion we covered where we were up to, the
(new) road map, and what we plan to achieve over the next two weeks, as
well as some longer term plans. See retrospective and iteration plan,
below. Longer term, we aim to get a talk on Fable to the Debian
miniconf in Cambridge in November.
For the miniconf, we'll want Debian packages, and possibly snaps, and
the tooling should be less of a prototype, but it doesn't need to be
production ready, yet.
We also both mentioned Fable to others, and there seems to be some
tentative initial interest.
We agreed that only code blocks at the top level will be supported for
fable scenario snippets. If we want to add support for them in, say,
list items, we can consider that when there is an actual user request.
We discussed tracking requirements for a moment, but agree that it's a
post-November thing for Fable. We need to keep scope limited to make
progress.
Fable branding may be relevant for the November presentation, but it's
not something we need to worry about before the BBQ.
At or after the August BBQ, we may want to recruit someone who's good
a typesetting or LaTeX.
Retrospective
=============
Lars has written (drafts of) two sample documents, the tutorial, and
an architecture document. The document generator seems to work
sufficiently well. The code generator (in Python, for Python) works
enough for one sample document.
Daniel has investigated Rust crates for parsing Markdown, and has the
beginnings of code that parses and then recreates it. Also, the code
can extract fable code blocks. This is a first step of being confident
we can parse and manipulate Fable documents. Unfortunately, the
pre-1.0 crate has just changed its API, so this work will need to be
re-done.
Iteration plan
==============
Lars
----
1. Implement the jt fable so it runs successfully.
1. Write some preliminary scenarios for the architecture document.
1. Style HTML output a little.
1. Style website a little.
1. Check that the installation instructions in the tutorial work.
1. Add to the tutorial a request to give us feedback on Fable and the
tutorial.
Daniel
------
1. Update the rust poc tool to adapt to markdown crate changes.
1. Ask our mutual friend R. M. to follow the tutorial and give us
feedback.
|
