Aleksandra Nenadic

Rename virtual environment - use different name to “venv” since it can be confusing for learners

3

We could have “venv*” in gitignore and “venv_xyz” as the name of the venv. Despite the convention, we should go with clarity for learners.

Update instructor notes - they are a bit outdated.

Agree on a release process [governance]

1

Development branch, release process and notes, frequency, etc. not that we may have more collaborators and more people using the course.

Switch to using VS Code

7

Rework the lesson material to use VS Code. Check that we have all the functionality available to us before the switch.

Improve flow of the lesson in sections 4 and 5

2

A couple of issues: - do we need to fork the software repo - are we looking at past commits prior to forking at all? - we talk about releasing...

Update the lesson to use the new lesson template

2

The new lesson template - [The Carpentries Workbench](https://carpentries.github.io/sandpaper-docs/). [Translation guide](https://carpentries.github.io/sandpaper-docs/migrating-from-styles.html) available.

Improve episode on packaging

2

Expand on this episode, this came out of the NERC workshop in Manchester 18-22 March and Aman Goel (an RSE from Mcr) promised he'd make a contribution.

Note warning when running CI tests, will need updating for next version of course: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2....