Remove outdated content

[bouweandela]

Remove outdated content

[egpbos]

When we are done with this issue, we may need to remove the sentence that may be added through #285 about the outdated sections ;)

[egpbos]

I will open a separate issue for this.

[egpbos]

Things to remove:

• Checklist: remove completely.
• Version control: Policy -> PMP, "we use GitHub" as well.
• Code quality
• Code reviews
• Licensing: "we use Apache v2" -> PMP. Rest is in Turing Way.
• Communication: already in PMP: output management.
• Testing
• Releases
• Documentation: update & move to Turing Way.
• Standards: 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.
• Teamwork
• NLeSC specific stuff:
  • Only keep chapter owners in chapters themselves
  • Projects
  • Checklists
  • E-infrastructure
• Intellectual property: -> PMP already in IP policy and Turing Way

Keep:

• UX
• Language guides: need update!

Add:

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

[LourensVeen]

I think IP already went to the Turing Way, and anyway we have our IP Policy. Does that leave anything for the PMP?

[egpbos]

Yes, you're right, thanks!

[egpbos]

One part of the e-infrastructure Guide that may be useful to keep is https://guide.esciencecenter.nl/#/nlesc_specific/e-infrastructure/e-infrastructure?id=security-and-convenience-when-committing-code-to-github-from-a-cluster, what do you think @bouweandela @c-martinez? Not sure where to put it, though.

For reference, the rest of it is duplicated here btw: https://nlesc.sharepoint.com/sites/home/SitePages/Access-to-Infrastructure.aspx

[bouweandela]

The github documentation also explains how to set this up: https://docs.github.com/en/authentication/connecting-to-github-with-ssh