USEPA/EPATADA

Publishing TADA via CRAN and ROpenSci

cristinamullin opened this issue · 4 comments

cristinamullin commented

Is your feature request related to a problem? Please describe.

Let's work on getting TADA published via CRAN. Then we can also publish it via ROpenSci.

Note from Justin B: "pyOpenSci is actually modeled after ROpenSci, I think Jeff Holiister and Laura DeCicco are both editors for it. CRAN will make it more visible/accessible, ROpenSci will help with code standards and infrastructure that make it more maintainable. You’re already using a lot of that infrastructure but a worthwhile review after CRAN. Let me know if I can be helpful on either front".

https://ropensci.org/software-review/

Describe the solution you'd like

Let's use this issue to plan next steps and track progress on a CRAN submission.

cristinamullin commented

To start, we must address all issues, including notes produced by this more robust CRAN check:

devtools::check(manual = TRUE, remote = TRUE, incoming = TRUE)
cristinamullin commented

We must pick a new name for the TADA package, because tada is already a taken/published package on CRAN:
image

erg-hzhou commented

I suggest you consider using EPATADA as the package name in CRAN. See an example - https://cran.r-project.org/web/packages/epanet2toolkit/index.html

  • 👍1
cristinamullin commented

I agree and have implemented this change in the cm-release-review-2 branch for both the package and shiny app. Plan to merge in next week after team review.