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

Clean-up and replace Communication chapter #380

Open
2 of 4 tasks
Tracked by #374
egpbos opened this issue Dec 3, 2024 · 3 comments
Open
2 of 4 tasks
Tracked by #374

Clean-up and replace Communication chapter #380

egpbos opened this issue Dec 3, 2024 · 3 comments
Labels
Milestone

Comments

@egpbos
Copy link
Member

egpbos commented Dec 3, 2024

  • 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...)
@egpbos egpbos added this to the v1.0 milestone Dec 3, 2024
@egpbos egpbos added the dash label Dec 3, 2024
@egpbos
Copy link
Member Author

egpbos commented Dec 4, 2024

Because of the NLeSC-internal reference, this should wait until #394 is merged.

@egpbos egpbos added the blocked label Dec 4, 2024
@egpbos
Copy link
Member Author

egpbos commented Dec 4, 2024

#394 is merged, this issue is unblocked.

@egpbos egpbos removed the blocked label Dec 4, 2024
@egpbos egpbos self-assigned this Dec 4, 2024
@egpbos
Copy link
Member Author

egpbos commented Dec 4, 2024

I'm not sure whether this should go in the software best practices chapter. The communication chapter used to contain points like:

  • have a home page
  • have a discussion list
  • make a demo docker image
  • make an online demo (where applicable)
  • do a screencast (e.g. on youtube)

While these are all great tips, I feel like this is more about community building. What do others think?

In view of time, I suggest we leave it out for the v1.0 release.

@egpbos egpbos removed their assignment Dec 4, 2024
@egpbos egpbos moved this to In review in Guide sprint Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In review
Development

No branches or pull requests

1 participant