-
Couldn't load subscription status.
- Fork 96
WIP: Update usage-policy.md #2658
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
base: master
Are you sure you want to change the base?
Conversation
Added first draft of Course resource request policy.
Fixing the formatting. bullets were incorrectly rendered.
|
Should we mention the maximum amount and type of resources that can be requested? |
|
We have a bunch of pages that partly touch the topic of how to organize a course on HPC:
For Noppe there are good pages covering the topic. I think we are really missing one page under computing where we have documentation for organizing a course, with links then to the correct places and a description of the overall process. (computing/course usage or something like that). Part of the things on this policy could be there instead, like the fact that you have to queue, and that you should perhaps get a reservation. |
|
Totally agree. How would you like to proceed? Shall we keep this information here or perhaps move to entirely own page? Or create a new topic and gather all the spread knowledge as walkthrough-link-list in there? I'm a bit reluctant to touch the docs.csc.fi HPC part myself 😁 edit: I mean I have no objection to provide content, but making decisions of new topics in the structure etc. Perhaps @rkronberg could lend his 🧠 |
|
Agreed, I think it is good to keep the usage-policy page as concise as possible. There is a lot of scattered info related to courses, so having a separate "index page" to collect this info is a good choice. I can make some proposal of a new page under /computing section. |
Added first draft of Course resource request policy.
Proposed changes
Briefly describe the changes you've made here. Remember to add a link to the preview page of your branch.
Checklist before requesting a review