unfmontreal / unf_support Goto Github PK

• Add more info in the README.
• Add a code of conduct markdown with link in the README.
• Specify in the README that the repo is public and no private information on MRI acquisition , no user login/password should be posted in the issues. (including ID, images, screenshots,... )

context

many times when i'd like to add someone from the unf team to an email conversation where 'unf-support' is cced, i don't know if that someone is already included in 'unf-support'.

suggestion

adding a section "unf-support email" in the README that lists the people who are included in this email. Or better (if privacy limitations allow it): link to the piece of code that hard-code these individuals so that it is dynamically updated (and the README is not out-of-sync)

ref: https://docs.computecanada.ca/wiki/Accessing_CVMFS

• create a 2 tier config where the main cache is on sequoia and each machine has a cache on the local scratch.