Open jsteyn opened 2 years ago
1. "Boilerplate" info for who we are and what we do! When I covered I did a "We're the RSE team and we run Software Carpentries workshops" kind of spiel off the top of my head, but it'd be good to have access to a template for this.
2. How to keep to time Again, from my own experience. I think we had a really big class that time, which took us all behind, but I was stopping every 10 minutes to help the lowest common denominator in the class who were struggling, while the ones who had finished sat around getting bored for most of the day. How do we manage this balance?
I've never been happy or clear with how we are supposed to offer the exercises (over Zoom/in person). I have spent tedious hours extracting the exercise markup from the workshop material and hosting this separately on my own GitHub pages, to which I have pointed participants via the workshop chat. I feel like I should not be wasting time doing this. The way the material is structured, however, means that unless particpants have exactly the same material in front of them as the instructors (which seems to me undesirable?) the exercises aren't readily accessible unless the instructor does share screen (on Zoom) or displays them on the main overhead (in person), both of which mean the drop-down solutions aren't available to particpants when they want them.
When I did my checkout lesson for the instructor course I copied the contents of the lessons into Jupyter notebooks, leaving blank code blocks for the all of the live coding and exercises. I thought this might help students flicking between the notes and being able to follow along. I think the session I helped out at just had a blank notebook on the instructors screen without any notes so students needed to go between the two themselves. Just a thought on maybe making it a bit easier for the students to follow along. I guess this mainly only works for the python session though.
Can we have a spreadsheet of who is doing which Carpentries session and when, pinned to the training materials Slack channel? It would just make quick access easier.
Is having software setup instructions on the workshop website potentially confusing as we don't actually need/want(?) them to do this? If we want to keep, perhaps we can add a line at the start saying these instructions are if you want to do the setup yourself in the future?
Administration
Running a workshop
JupyterHub