summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2019-07-31 10:24:15 +0300
committerLars Wirzenius <liw@liw.fi>2019-07-31 10:24:15 +0300
commitb9b647f5f7a0c333775f12c2bf21bb044a5a4616 (patch)
tree8dec479529040e8e6f462ba62ea85b6dd008adb4
parent1136fc7cc476dad8fca6db5b304378cea55fb17e (diff)
downloadfable.liw.fi-b9b647f5f7a0c333775f12c2bf21bb044a5a4616.tar.gz
Add: iteration notes from Saturday
-rw-r--r--iterations/20190727-to-20190810.mdwn60
1 files changed, 60 insertions, 0 deletions
diff --git a/iterations/20190727-to-20190810.mdwn b/iterations/20190727-to-20190810.mdwn
new file mode 100644
index 0000000..5040c0b
--- /dev/null
+++ b/iterations/20190727-to-20190810.mdwn
@@ -0,0 +1,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.