async iteration planning meeting

This changes the usual meeting minutes structure a little bit:

* The "assessment of iteration" now includes a review of actions. This
  avoids an extra top level heading.
* The repository review is now a table and includes counts of closed
  issues and MRs.

I hope these will make it easier to skim memos in the future.

Sponsored-by: author

1 files changed, 119 insertions, 0 deletions

diff --git a/blog/2022/12/03/planning.mdwn b/blog/2022/12/03/planning.mdwn
new file mode 100644
index 0000000..98c1bf4
--- /dev/null
+++ b/blog/2022/12/03/planning.mdwn
@@ -0,0 +1,119 @@
+[[!meta title="Iteration planning: December 03–17"]]
+[[!meta date="2022-12-10 15:30:00 +0000"]]
+[[!tag meeting]]
+
+[[!toc levels=2]]
+
+# Assessment of the iteration that has ended
+
+We had the following actions from last time
+
+- **NOT DONE:** Daniel to write up an issue describing configurable templates, how they would
+  look from the user perspective, and from an implementation perspective.
+  Then to request feedback from Heiko.
+- **NOT DONE:** Once that's done, Daniel or Lars to write standalone mode for Rust template.
+- **NOT DONE:** Lars to try to use the Markdown parser he wrote for his static site
+  generator for Subplot.
+
+We had chosen the following issues for this iteration:
+
+- **NOT DONE:** [[!webissue 4]] -- _Review FAQ_
+- **NOT DONE:** [[!subplotissue 305]] -- _Maybe create binary releases?_
+- **DONE:** [[!subplotissue 310]] -- _Subplot uses clap v3, should use clap v4_
+
+We didn't get much done, but that happens.
+
+# Discussion
+
+## The gitlab.com hosting situation
+
+We reviewed [the billing
+page](https://gitlab.com/groups/subplot/-/billings) for Subplot on
+gitlab.com. It all looks OK. We're over the limit on seats, but it
+seems we can increase the seats for free.
+
+We will review the billing page every iteration or two.
+
+## Repository review
+
+We reviewed issues updated since the previous
+meeting, merge requests, and CI pipelines for all the projects in the
+[Subplot group](https://gitlab.com/subplot) on gitlab.com.
+
+| Repository                                                                      | Open issues | Closed issues | Open MRs | Closed MRs |          CI |
+| :------------------------------------------------------------------------------ | ----------: | ------------: | -------: | ---------: | ----------: |
+| [subplot-container-images](https://gitlab.com/subplot/subplot-container-images) |           1 |             4 |        0 |          3 | OK (GitLab) |
+| [subplot-web](https://gitlab.com/subplot/subplot-web)                           |           1 |             0 |        0 |         73 |    OK (Ick) |
+| [subplot](https://gitlab.com/subplot/subplot)                                   |          44 |           265 |        0 |        303 | OK (GitLab) |
+
+Extra branches:
+
+- `subplot` branch `docgen-cmark` — Lars is keeping this around for reference for
+  future changes
+
+## Recurring items issues
+
+There are some issues tagged
+[`recurring-agenda-item`](https://gitlab.com/groups/subplot/-/issues/?sort=created_asc&state=opened&label_name%5B%5D=recurring-agenda-item&first_page_size=20)
+in the issue tracker, which we discuss in every iteration meeting.
+
+- [[!subplotissue 119]] -- _Subplot is in not in Debian unstable_
+  - we will work on reducing Subplot dependencies that aren't already
+    in Debian
+  - need the dependency list; we are not targeting bookworm
+
+# Goals
+
+## Goal 3: Current goal
+
+Subplot is altered to treat a YAML document as the root of any subplot
+document, permitting multiple markdown files to be joined into a
+single scenario set or output document. We remove our dependency on
+Pandoc’s AST for internal document representation, and support a
+better range of document metadata as a result. We will use marked data
+types where possible to permit better provenance information in error
+and warning messages; and we will strive to reenable the reference
+tests such that we can make a statement to the effect that post goal
+3, we do not intend to make further breaking changes to the input
+formats or primary behaviours of Subplot.
+
+([Related issues on gitlab](https://gitlab.com/subplot/subplot/-/issues?label_name%5B%5D=goal%3A%3A3))
+
+## Goal 4: Planned
+
+This goal is very likely to change. This is merely an initial sketch.
+
+We'll improve documentation and generally aim at making Subplot more
+plausibly usable by people outside of the Subplot project.
+
+([Related issues on gitlab](https://gitlab.com/subplot/subplot/-/issues?label_name%5B%5D=goal%3A%3A4))
+
+# Plan for new iteration
+
+## Issues
+
+This month is, as is traditional, filled with all sorts of other
+obligations. We decided to carry over actions and issues from the
+previous iteration, and to make it a longer one.
+
+We intend to work on the following issues
+([[!ms 8]]), mostly carried over from the previous iteration:
+
+- [[!webissue 4]] -- _Review FAQ_
+- [[!subplotissue 305]] -- _Maybe create binary releases?_
+
+## Actions
+
+These are in addition to work on issues chosen for this iteration.
+
+- Daniel to write up an issue describing configurable templates, how they would
+  look from the user perspective, and from an implementation perspective.
+  Then to request feedback from Heiko.
+- Once that's done, Daniel or Lars to write standalone mode for Rust template.
+- Lars to try to use the Markdown parser he wrote for his static site
+  generator for Subplot.
+
+# Meeting participants
+
+- Daniel Silverstone
+- Lars Wirzenius