Subplot → blog → 2021 → 04 → 24 → Iteration planning: April 24th
  1. Review of actions from last meeting
  2. Review of the iteration that has ended
  3. Review of the repositories
  4. Issue review
  5. Current goal
  6. Plan for next iteration
  7. What do we need to persuade others?
  8. Other business
    1. Whole codebase review of Subplot
    2. Subplot organisation on Gitlab
    3. Using Gitlab CI pipelines for subplot
  9. Actions

Review of actions from last meeting

Review of the iteration that has ended

We made good progress on Subplot milestone 26.

We achieved:

We did not complete Subplot issue 173 (or rather there is pending queries against it), and while we made progress on Subplot issue 127 we are not finished with it yet. Subplot 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 (Subplot merge request 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.

  • Subplot issue 22 was tentatively put into the new iteration
  • Subplot issue 176 was tentatively put into the new iteration and assigned to Daniel
  • Subplot issue 74 was subtly retitled to indicate bash is the only waiting impl.
  • Subplot issue 118 was tentatively put into the new iteration and assigned to Lars
  • Subplot 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.
  • Subplot 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.
  • Subplot issue 141 we added the someday-maybe label
  • Subplot issue 160 we linked Lars’ release notes for his personal projects
  • Subplot issue 163 Daniel ticked the first TODO item.
  • Subplot issue 177 was tentatively put into the iteration
  • Subplot issue 178 was tentatively put into the iteration and assigned to Daniel
  • Subplot issue 179 we added mentor and feature.
  • Subplot issue 180 we added a comment about maybe how to achieve this. We also labelled it someday-maybe.
  • Subplot 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
  • Subplot issue 182 we tentatively added to the iteration and assigned to Lars
  • Subplot issue 183 we tentatively added to the iteration and assigned to Lars
  • Subplot issue 184 we added the documentation tag
  • Subplot 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 Subplot 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 Subplot 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 Subplot issue 22.

  • Move the subplot-web and subplot repositories to the new subplot organisation at some point during the iteration.