Oct 17th, Core team meeting minutes

[Crosita]

Agenda:

• meeting minutes: start rotation
• progress container and validation report
• follow up r-multiverse meeting
• conference Phuse US march 2025: send new abstract?

[xinye1]

Meeting notes:

• A quick replay of last meeting notes around r-multiverse and conferences
• 11th Nov virtual conference on workstream progress on container and reports
• Container update
  • Beginning of test image, there's an approach to trigger build
  • Currently project is stored in persona repo (mmengelbier/wg-testimage)
  • Decided to build a basic test image instead of layers which would cause issues with long runs
  • Run needs to be complete within 6 hours due to GitHub token
  • Need to confirm the files that are part of the commit (related to the "validation scope"?)
  • Not yet decided is the place to store the results - related to the specific tests - current thinking is writing back to repo, or as part of release notes, questions
    • is this the right approach
    • how to deal with multiple packages, loop / parallel?
  • Logistics - install is currently temporary, how to persist
  • System dependency is currently simple and potentially hacky, potentially requires refinement
  • Trigger files: e.g. using pak file
  • Results could use process, run ID etc. for reference, need to cautious of overwriting
  • Core of GHA is located jobs:test_packages:container:latest-rockylinux
  • Reporting - an idea is to be triggered from the build job completion
  • Output summary metrics - should this be captured by a SQLite database + separate files? The run is ephemeral and DB could be destroyed after run.
  • To be continued ...