Background:

• Reference Tendler et al. 2023 https://doi.org/10.7554/eLife.88853

Activities:

• Create a GitHub organization
• Brief intro to Quarto books
• How to use our template step-by-step

Maybe this is a two-session thing. 1 is discuss need for lab handbook and brainstorm stuff that should be in it, 2 is create book and begin editing

It would probably be useful if all of these followed a common format. E.g. the same section headings ("pre-requisites", "homework", "leader notes", or whatever). Possibly separate materials for leader and group members? Possibly slides for group leader to present?

What other lab-level trainings should there be?

In the peer code review lesson, add a download button for the rubric table. Probably should store this as a csv and include in both the book and download programmatically so only needs editing in one place.

• Whittle down potential offerings list
• Give them a better description
• Give the whole thing a title ("lab guides for reproducibility"?)
• Give the whole thing a description

They have several offerings—are any of them similar to what we're thinking of?

I think it would be beneficial to include a link to and summary of this preprint: https://doi.org/10.31234/osf.io/8k5a4

Might even be good to attempt to include some (optional) versions of the interventions they mention. E.g. brainstorm thoughts and feelings around peer code review to increase self-awareness, practice cognitive restructuring (re-phrase negative thoughts in constructive and self-compassionate ways), and mention that exposure is important (if code review is scary, you should do it more often