Closed SJaffa closed 5 months ago
Thank you for your pull request :smiley:
:robot: This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.
If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
:mag: Inspect the changes: https://github.com/carpentries-incubator/fair-research-software/compare/md-outputs..md-outputs-PR-23
The following changes were observed in the rendered markdown documents:
01-fair-research-software.md | 24 +++++++++++++++++++++++-
md5sum.txt | 2 +-
2 files changed, 24 insertions(+), 2 deletions(-)
:stopwatch: Updated at 2024-03-01 16:01:53 +0000
I like these icebreaker discussions - as you say they may be suitable at the intro to the course episode (I made a PR: https://github.com/carpentries-incubator/fair-research-software/pull/22 for that) during jargon busting. Similarly, you may want to move the last section of the intro episode (called "FAIR software") into your first episode). Let's have a chat about this later today and make a decision and then move things around accordingly.
New structure:
The FAIR list:
Expand "accessibility" a bit to include readability (does it make sense once you got it). Expand "reusability" to include being able to run the code on different platforms/operating systems (which is mentioned in the paragraph above the list).
Added an icebreaker discussion (although that might be better in the course intro lesson) and some exercises to get people thinking about how FAIR principles applies to their own work