Licencing

[anenadic]

• Extracted some of the licensing comment into an extra episode to create space for covering virtual environments
• Covered the basics of licensing in the documentation episode, including the exercise to add a LICENSE file

[github-actions[bot]]

Thank you!

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:

• :dart: correct output
• :framed_picture: correct figures
• :question: new warnings
• :bangbang: new errors

Rendered Changes

:mag: Inspect the changes: https://github.com/carpentries-incubator/fair-research-software/compare/md-outputs..md-outputs-PR-131

The following changes were observed in the rendered markdown documents:

 07-documenting-code.md   |  80 +++++++-
 08-open-collaboration.md | 491 ++---------------------------------------------
 config.yaml              |   1 +
 licensing.md (new)       | 385 +++++++++++++++++++++++++++++++++++++
 md5sum.txt               |   8 +-
 reference.md (gone)      |  84 --------
 6 files changed, 479 insertions(+), 570 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

:stopwatch: Updated at 2024-08-12 15:10:24 +0000