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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
[[!meta title="Iteration planning: January 31sh"]]
[[!tag meeting]]
[[!meta date="2021-01-31 09:52"]]
[[!toc levels=2]]
# Review of the iteration that has ended
We completed all the work we'd hope on getting done for [[!milestone
21]], except for the pairing with Dan on [[!issue 22]. It was not a
huge iteration, but that's OK. It's still movement forward.
# Review of the repositories
There were no pending merge requests, either for subplot itself or subplot-web.
There were no extra branches, either in subplot itself or subplot-web.
We reviewed all issues and updated them as needed.
# General discussion
## Using issues to track work for an iteration
We noted that we often take on issues in an iteration with no plan to
complete all the work for the issue in that iteration. We don't really
track that well. We decided that we'd start using sub-issues in the
future, and create an issue for the work we plan for the iteration.
## Setting goals
We discussed setting a specific goal for an iteration, but decided
against it. Instead, we'll set a goal for the next few iterations,
something we believe we'll be able to reach within that time frame. We
feel that having an explicit goal like that will give better focus for
our work and planning of that work.
## Making releases
We discussed making releases of Subplot and agreed that it would be a
good thing to do. We opened [[!issue 160]] to discuss that.
## Treating build-time warnings as errors
We discussed whether Subplot's automated test suite should treat
warnings from the Rust toolchain as errors. We agreed that CI should
definitely do that, but that `./check`, our script for running the
test suite, should have an option to allow the warnings. Our reasoning
is that our development environments can have newer versions of Rust
than our CI, and it would be unpleasant to sprinkle the source code
with `#[allow]` pragmas just to silence new warnings, even during
development cycles. ([[!issue 162]])
## Roadmap
The roadmap on the Subplot website is quite obsolete. We discussed
this and decided that we'll remove it for now. We may put one back
once we start making releases, and have the roadmap cover at least one
release in detail, and possible a few releases at less detail.
# Current goal
Our current goal is to get Subplot the software and project into such
a shape that we feel confident that we can ask a few people to give it
a proper try. This requires for Subplot to have releases that are be
easy to install, tolerably easy to use, and to have at least some
rudimentary documentation aimed at beginners.
# Plan for next iteration
We created [[!milestone 22]] for the iteration starting now and ending
in two weeks on 2021-02-13.
We picked the following issues to work on for Lars:
* [[!issue 97]]
* [[!issue 116]]
* [[!issue 152]]
* [[!issue 157]]
* [[!issue 159]]
For Daniel:
* [[!issue 148]] (see action note below)
* [[!issue 156]]
* [[!issue 158]]
* [[!issue 161]]
Up for grabs if anyone has time:
* [[!issue 22]] depends on Dan's availability.
* [[!issue 153]]
* [[!issue 155]] is a tracking issue, to be closed once its sub-issues
are closed.
# Actions
* Lars or Daniel to schedule pairing session with Dan to help him work
through [[!issue 22]].
* Lars to remove the roadmap from the Subplot website.
* Daniel to turn [[!issue 148]] into a tracking issue.
* Daniel to file an issue to create issue templates based on
<https://third-bit.com/2021/01/18/how-to-write-a-memo/>.
|
