Review of actions from previous meeting

Actions from last time, and their status are:

• DONE: Daniel will review Lars’ gripes and look to file appropriate issues to cover correcting the problems
  • no actual issues filed yet
• DONE: Between Daniel and Lars - the talk will be drafted.

Review of the iteration that has ended

Subplot milestone 42 represented this iteration.

We completed:

• Subplot issue 259 Top level subplots should be run in Rust too
  • subplot.md is now run with the Rust step functions, via cargo test
  • we now have bindings files that work for both Python and Rust for the lib/files and lib/runcmd libraries that come with Subplot

We made some progress on:

• Subplot issue 251 We depend on a vulnerable version of chrono
  • upstream hasn’t released a fix
  • Lars looked at dropping chrono as a dependency, but couldn’t find a reasonable way to do that, and then gave up
• Subplot issue 252 We transitively depend on a vulnerable version of time
  • this is basically just a duplicate of the chrono issue

We made no progress on:

• Subplot issue 133 No feature table comparing scenario runners from different codegen templates

We moved the open issues to the milestone for the iteration staring and then closed off this iteration.

Review of the repositories

Currently open MRs:

• subplot: none
• subplot-web: none
• subplot-container-images: none

Extra branches unrelated to MRs:

• subplot:
  • subplot-rust – Daniel is keeping this around until he has completed the work on Subplot issue 141.
  • docgen-cmark – Lars is working on making docgen use cmark rather than pandoc for the initial parse and processing.
• subplot-web: none
• subplot-container-images: none

Pipelines:

• subplot: clean
• subplot-web: none
• subplot-container-images: clean, and we triggered the one to build a new container image

Current goal (goal 2; not changed for this iteration)

Subplot provides a set of libraries with identical capabilities in each of the supported languages. Python remains a supported language. Rust is promoted to supported-language status. Subplot will be tested with all supported languages. In addition, any quality of life improvements which can be done shall be done. This goal will be considered complete when a release of Subplot has been made with the unified language handling support complete.

Issue review

We had 58 open issues at the start of the meeting.

We reviewed all issues for subplot, except ones labelled someday-maybe. There were 29 of these.

We made a few additional comments and adjusted labels.

We left the docker-for-subplot issue alone, and subplot-web had no issues.

Plan for next iteration

We opened Subplot milestone 43 to cover this iteration, with the following issues:

• Subplot issue 133 No feature table comparing scenario runners from different codegen templates
• Subplot issue 221 Command line tool has insufficient logging
• Subplot issue 243 Doesn’t do “and” automatically
• Subplot issue 248 In Rust runcmd, write exit, stdout and especially stderr upon failure
• Subplot issue 251 We depend on a vulnerable version of chrono
• Subplot issue 252 We transitively depend on a vulnerable version of time

Other business

Talk at FOSDEM on Subplot

Daniel has talked to safety people at his work and gotten valuable feedback for the talk. He wants to have a finished draft of the talk, ready for recording, by the end of this iteration. Lars will be available for review.

Release plan for this iteration

We decided to defer making a release of whatever is in the main branch until we have done our talk. When we do, we’ll label it 0.3.2 or 0.4.0, depending on whether it has breaking changes or not. Subplot issue 254

Getting Subplot into Debian

We are not yet ready to file an RFP bug to get Subplot packaged for Debian. It will happen after we think we won’t be making breaking changes anymore. We probably want to do a review of the dependencies as well, to make packaging easier.

Review of the whole code base of Subplot

We are not yet ready to make a whole code base review of Subplot. However we feel at least part of goal 3 will be reviewing a portion of the code.

Issue based agenda

We will switch an issue based agenda when other people join the meeting.

Reaching out for feedback

We won’t be reaching out for feedback until goal 3 is done.

A media repository

Regarding the media repository question - we believe this is premature at this point - once we are ready to write the talk mentioned above, it will be time for the repository.

Convincing to try Subplot

No new thoughts yet.

Actions

• None.