NCoVUtils
NCoVUtils copied to clipboard
epiforecasts
Name change for package
The current name is not good (esp the random V). Is there a good way to change a package name beyond copying the repo, changing the name and then redirecting everything to the new package repo?
Does anyone have suggestions for a good name?
It is possible to rename a GitHub repo (and then update the DESCRIPTION etc. accordingly), but I think it's safer to just copy to a new repo like you suggest — to avoid breaking workflows of users that prefer not to update.
Here are some general thoughts on package naming from rOpenSci and Hadley Wickham. In summary: keep it short, single case (generally lowercase), and Google-able.
Some quick ideas (all available on CRAN based on available::available()):
- covdata
- covutils
- covidutils
- covidr
Somewhat related, the rgamma/rweibull functions stand out to me as separate from the main 'theme' of the other functions, which all relate to data import. Could consider splitting the package into two: one focused on data import, and one focused on other utils.
Agree on the copy and rename.
Sounds like Hadley will not be onboard with our Epi- series 😄
My preference here is covdata I think as I see this really moving towards the data side of things.
Agree on the sampling functions - those were mainly just shoved in during the first few weeks crush and aren't really used by any current analysis as far as aware. Suggest drop when the name is changed.
Anyone else have a name preference?
Just came across this other covdata package on GitHub, which imports ECDC and US state-level data. So might want to avoid that name.
Damn and they have a badge.
Next suggestion: getcovdata -> gets at the fact we contain no data and just serve other peoples hard work (which is super important to highlight).