summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2019-07-13 19:46:28 +0300
committerLars Wirzenius <liw@liw.fi>2019-07-13 19:46:28 +0300
commit6bf1f5b54f543f490560091e700dcbfc9d4abe7c (patch)
tree73050580c769756c6c328d30c0a7d7e8c33d5985
parent90324f68a5d975f1ad3773d152898a996e2a4b14 (diff)
downloadfable.liw.fi-6bf1f5b54f543f490560091e700dcbfc9d4abe7c.tar.gz
Add: iteration meeting notes, roadmap update
-rw-r--r--iterations/201906713-to-20190727.mdwn63
-rw-r--r--roadmap.mdwn3
2 files changed, 65 insertions, 1 deletions
diff --git a/iterations/201906713-to-20190727.mdwn b/iterations/201906713-to-20190727.mdwn
new file mode 100644
index 0000000..573b247
--- /dev/null
+++ b/iterations/201906713-to-20190727.mdwn
@@ -0,0 +1,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.
diff --git a/roadmap.mdwn b/roadmap.mdwn
index eac3430..74d5467 100644
--- a/roadmap.mdwn
+++ b/roadmap.mdwn
@@ -35,6 +35,7 @@ August BBQ we're going to.
- samples
codegen_rs:
+ status: next
label: |
We have started on a
code generator in Rust
@@ -74,7 +75,7 @@ August BBQ we're going to.
- samples
website:
- status: next
+ status: finished
label: |
There is a website that
we can point people at,