ctb
commented
3 years ago related: what suggestions are there to support the underlying infrastructure needed, i.e. persistence of files?
we could specifically focus on supporting institutional HPC and provide guidance for HPC folk as to where and how to set up files and adjust results and so on.
we could try to rework the material to support multiple "endpoint systems" - binder, cloud instances, and HPCs - not sure if the material ends up being coherent tho.
we keep on teaching and re-teaching similar bits of this material!
there is a world in which this material continues to evolve (and improve) while being repurposed for various things. that world sounds like a good one to me?
specifically, for stuff that my lab drives,
could serve as a supported set of material for teachers who want to teach some or all of this at their own institution, in their own workshops series, etc.
what additional kinds of support would be useful?
what technical approach?
one way to do this is to create/maintain a base repository that is where modifications and upgrades to base material go.
then anyone can fork it, and customize it; but we could ask them/expect them to contribute back.
could turn it into a template a la simon willison with cookiecutter and github actions, see https://twitter.com/simonw/status/1431708674498519040
important (IMO) to keep the basic URLs going for each offering. so a first step would be to rename this repo and then fork it back into this name, and support the current set of urls (https://ngs-docs.github.io/2021-august-remote-computing)
what social approach?
support explicit contributor guidelines, authorship notes, modification notes
state that publication of modifications would be fine :)