Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publishing TADA via CRAN and ROpenSci #452

Open
cristinamullin opened this issue Apr 30, 2024 · 4 comments
Open

Publishing TADA via CRAN and ROpenSci #452

cristinamullin opened this issue Apr 30, 2024 · 4 comments

Comments

@cristinamullin
Copy link
Collaborator

cristinamullin commented Apr 30, 2024

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
Copy link
Collaborator Author

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
Copy link
Collaborator Author

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

@erg-hzhou
Copy link
Collaborator

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

@cristinamullin
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants