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
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
[[!meta title="Iteration planning: April 24th"]]
[[!tag meeting]]
[[!meta date="2021-04-24 18:30"]]
[[!toc levels=2]]
# Review of actions from last meeting
- Dan remains not in a position to work on [[!issue 22]], which is
fine, it can wait until he is able to help. We're carrying this
action
- Daniel to file an issue to create issue templates based on
<https://third-bit.com/2021/01/18/how-to-write-a-memo/>. This is
now done as [[!issue 184]]
# Review of the iteration that has ended
We made good progress on [[!milestone 26]].
We achieved:
- [[!issue 175]]
- [[!issue 174]]
- [[!issue 171]]
- [[!issue 169]]
- [[!issue 161]]
- [[!issue 137]]
- [[!issue 116]]
- [[!issue 108]]
We did not complete [[!issue 173]] (or rather there is pending queries against
it), and while we made progress on [[!issue 127]] we are not finished with it
yet. [[!issue 22]] is carried.
# Review of the repositories
There were no pending merge requests for subplot-web. There is one MR in subplot
outstanding wrt. `pandoc_ast` ([[!mr 155]]). There are no vestigial branches.
# Issue review
Subplot-web has no open issues.
We reviewed all open issues this time around. Where we made changes, see below.
- [[!issue 22]] was tentatively put into the new iteration
- [[!issue 176]] was tentatively put into the new iteration and assigned to Daniel
- [[!issue 74]] was subtly retitled to indicate `bash` is the only waiting impl.
- [[!issue 118]] was tentatively put into the new iteration and assigned to Lars
- [[!issue 126]] we added a note that this can be closed once we have documented
the decision (and mechanism) of updating the dependencies in the release cycle.
- [[!issue 127]] we had moved over to the new iteration, and we agreed that
Lars will either close it, or update it with what more needs doing at some
point during the iteration.
- [[!issue 141]] we added the `someday-maybe` label
- [[!issue 160]] we linked Lars' release notes for his personal projects
- [[!issue 163]] Daniel ticked the first TODO item.
- [[!issue 177]] was tentatively put into the iteration
- [[!issue 178]] was tentatively put into the iteration and assigned to Daniel
- [[!issue 179]] we added `mentor` and `feature`.
- [[!issue 180]] we added a comment about maybe how to achieve this.
We also labelled it `someday-maybe`.
- [[!issue 181]] Daniel added a description of where we are and what we should do.
We tentatively added it to the iteration and assigned it to Daniel
- [[!issue 182]] we tentatively added to the iteration and assigned to Lars
- [[!issue 183]] we tentatively added to the iteration and assigned to Lars
- [[!issue 184]] we added the `documentation` tag
- [[!issue 185]] we tentatively added to the iteration and assigned to Lars
# 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 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 27]] for the iteration starting now and ending
in two weeks on 2021-05-08.
We agreed with the assignments we had made in the review period, and we kept
[[!issue 22]] in case Dan turns up.
# What do we need to persuade others?
Nothing new came up. We're making progress, though.
# Other business
## Whole codebase review of Subplot
Lars brought this up - it's not relevant for the current goal, but he wanted to
bring it up for discussion now to let simmer and come up with a good approach
for how to do this. Daniel suggested we should write a high level software
architecture document since that would help us to understand the codebase's
structure. We will keep this as a permanent agenda item until we have achieved
a full codebase review.
## Subplot organisation on Gitlab
We created https://gitlab.com/subplot/ and made sure Daniel and Lars were both
owners. Importantly Daniel can create repositories etc. here.
When we move the subplot-web repository, we will have to update the website
mirroring. When we move the subplot repository we will have to update the
mirroring to Lars' server, the website's `shortcuts.mdwn` and any other external
links that we have, including any clones we have.
## Using Gitlab CI pipelines for subplot
We've decided to at least use pipelines to test MRs. In the future we may
choose to automate some of the release process with them, but since we have not
defined a release process yet, this is not for now.
# Actions
- Lars or Daniel to schedule pairing session with Dan to help him work
through [[!issue 22]].
- Move the subplot-web and subplot repositories to the new subplot organisation
at some point during the iteration.
|
