Name change
alimanfoo opened this issue · comments
Everyone's favourite question, what should we call this thing? 😄
Originally I called this environment "binder" because this made it convenient to then include this repo as a submodule on another repo, which would then play well with anyone wanting to use that other repo with the mybinder service.
However, we stopped using mybinder a while back, and so the "binder" name for this repo is really a historical oddity.
Can anyone think of a better name?
I wondered about "mgenv", which is riffing a bit on "stenv" (which incidentally is a very parallel project to this one, maintaining a conda environment for the space telescope institute).
Of course, no-one will know how to say "mgenv", which could be annoying or possibly mildly amusing :)
Of course there is always "malariagenv" :)
cc @leehart
I often use the abbreviation "mgen", which I pronounce "em jen".
+1 for mgenv (MalariaGEN environment)
The only potential clashes I've found so far are:
- An obscure Go package (v0.0.6) https://pkg.go.dev/github.com/elastic/go-txfile/dev-tools/lib/mage/mgenv
- "MGEnv is a simulated micro-grid domain modeled out of real data from the PecanStreet Inc. database." https://arxiv.org/pdf/1906.06178
Thanks @leehart, I think we should go for it, let's rename to "mgenv".
Shall we start afresh or literally rename via https://docs.github.com/en/repositories/creating-and-managing-repositories/renaming-a-repository ?
Should be able to rename this repo?
OK, I'll just rename this repo as it is.
Thanks @leehart. Should probably check the code too in case "binder" is still used anywhere, e.g., in environment names.