Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove outdated content #286

Open
bouweandela opened this issue Sep 20, 2023 · 7 comments
Open

Remove outdated content #286

bouweandela opened this issue Sep 20, 2023 · 7 comments

Comments

@bouweandela
Copy link
Member

Much of the content of the guide is outdated and/or has been moved to The Turing Way. I will make a start with removing this content, as it reflects poorly on the center.

@egpbos
Copy link
Member

egpbos commented Oct 17, 2023

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
Copy link
Member

egpbos commented Nov 1, 2023

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:

@LourensVeen
Copy link
Member

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

@egpbos
Copy link
Member

egpbos commented Nov 1, 2023

Yes, you're right, thanks!

@egpbos
Copy link
Member

egpbos commented Nov 3, 2023

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
Copy link
Member Author

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

@egpbos
Copy link
Member

egpbos commented Nov 7, 2023

I will open a separate issue for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants