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

Discussion: Include this documentation with the main Sheffield HPC documentation? #2

Open
jkwmoore opened this issue Apr 25, 2023 · 2 comments

Comments

@jkwmoore
Copy link
Contributor

Hi folks, as this is seemingly for getting things setup for ShARC / Sheffield HPC - is this something you'd want to or like to include within our main HPC documentation instead? https://github.com/rcgsheffield/sheffield_hpc

This will mean you can get a few more eyes over the documentation / TUOS IT Staff aligned with the HPC will be able to keep an eye on it and update it with our main documentation as things change to the systems we have.

Likewise for any documentation the Bioinformatics core thinks might suit being in our main HPC documentation.

@lquayle88
Copy link
Member

Personally not opposed to this idea; I was going to update everything when I setup nf-core on stanage but as I will be leaving in around a month (though still maintaining ties and UoS login all being well) who knows if and when this might happen. So probably good to have RSE behind nf-core on UoS HPCs

@jkwmoore
Copy link
Contributor Author

Sounds good to me, if you make some PR's against our docs on where you'd like things to sit in the directory tree we can look at getting that included soon.

e.g. we could have a community docs section with Sheffield Bioinformatics specific docs.

Hopefully our README is fairly good so converting from MD to RST under Sphinx should be relatively painless! That said, let me or one of the other maintainers on the docs know if you need a hand.

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

2 participants