docs issueshttps://git.geomar.de/data/docs/-/issues2017-08-24T08:52:37Zhttps://git.geomar.de/data/docs/-/issues/19Find a short name for all this?2017-08-24T08:52:37ZWilli RathFind a short name for all this?In writing the README's, I've noticed that a short name for "The group on git.geomar.de, the checkouts on Taurus et al, and the general idea behind all this." would make things easier.
From the original headline of <https://git.geomar.d...In writing the README's, I've noticed that a short name for "The group on git.geomar.de, the checkouts on Taurus et al, and the general idea behind all this." would make things easier.
From the original headline of <https://git.geomar.de/data/docs/blob/master/README.md> `Version Controlled Research Data at GEOMAR` we could derive acronyms like:
- VREDA
- VERDA
- VERDAG
- VERDAT
- VECDA
- DUCT (data under [version] control)
- ...
I'm somehow tending to leave "Geomar" out of the name.
@all: What do you think?https://git.geomar.de/data/docs/-/issues/14How to clearly define dependencies?2017-08-18T16:11:07ZWilli RathHow to clearly define dependencies?As, e.g., Git LFS is quickly evolving, we need to clearly define the dependencies.
I did all my tests with conda-forge/git and conda-forge/git-lfs.
Using a conda env for deployment and all / many of the tasks in the repositories themse...As, e.g., Git LFS is quickly evolving, we need to clearly define the dependencies.
I did all my tests with conda-forge/git and conda-forge/git-lfs.
Using a conda env for deployment and all / many of the tasks in the repositories themselves would also benefit from the usually up-to date conda-forge packages for netCDF, CDO, NCO etc.
@all: What do you think?