Test

[egpbos]

Straightforward replacements

Materials that were moved to the Turing Way that we want to map (using links to the Turing Way or RSQkit or other reputable sources) in the Best Practices chapter (see #321 and #360).

• Checklists #373
  • Add a section to Best Practices; the PR where it was removed contains links.
  • Remove the chapter PR
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Version control
  • Add a section to Best Practices.
    • NLeSC-internal note: refer to the PMP, "we preferably use GitHub".
  • Remove the chapter PR
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Code quality
  • Add a section to Best Practices.
  • Remove the chapter
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Code reviews
  • Add a section to Best Practices.
  • Remove the chapter
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Licensing
  • Add a section to Best Practices.
    • NLeSC-internal note: refer to the PMP, "we preferably use Apache v2".
  • Remove the chapter PR
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Communication
  • Add a section to Best Practices.
    • NLeSC-internal note: refer to the PMP, section "output management"
  • Remove the chapter PR
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Testing
  • Add a section to Best Practices.
  • Remove the chapter PR
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Releases
  • Add a section to Best Practices.
  • Remove the chapter
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Teamwork
  • Add a section to Best Practices.
  • Remove the chapter PR
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)
• Intellectual property
  • Add a section to Best Practices.
    • NLeSC-internal note: refer to the PMP, section "IP policy"
  • Remove the chapter: PR together with licensing
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)

A bit more work + replacements

Any tasks including keep, add or update don't belong here, but in their own issues.

• Documentation chapter

  • Update & move to Turing Way.
  • Add a section to Best Practices.
  • Remove the chapter
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)

• Standards chapter

  • Not really stressed in the Turing Way. Make issue there? Connect to code quality, mention FAIR. There's something about data standards. In Code Quality there's style standards. Should be more stressed: interoperability & reusability by using standards.
  • Add a section to Best Practices.
  • Remove the chapter
  • Afterwards: check for broken links (globally! the PR link checker only checks changed files...)

Add?

• Julia?
• Rust?
• Matlab?
• Go?
• Look into https://softwaresaved.github.io/international-survey-2022/country/world/#tools-and-programming-languages
• ML guide?