feedback from Patrick B.

[mkuzak]

• Licenses could be in the little wider module on IP.
• Separating testing from CI/CD, one thing is writing tests (even a simple working example / reproducible result is a test) another is the automation of tests. Unit and integration tests are most important.
• Missing: contribution, collaboration, managing an open source project, GitHub Flow (or similar example), code formatting, code style etc.
• project organisation: code organisation may be a better name
• HPC part is about scaling up
• organisation by motivation could be a good idea

[mkuzak]

and some more :)

Another thought about the course: I think many of the topics assume open source software, but this is not at all an obvious choice for many researchers. Perhaps open vs closed should be a topic on its own. FAIR is more about “how” than about “why”, so that would be step two, but first they need to be convinced of open sourcing at all. Or btw maybe not, there could be valid cases for closed source as well, but anyway, it’s a whole discussion filled with fear and emotion that probably is top of mind for many researchers and that supporters could help with.