CRAN submission - Githubissues

getwilds / rcromwell

R client for interacting with Cromwell with WDL workflows

http://getwilds.org/rcromwell/

Other

4 stars 2 forks source link

CRAN submission #28

Open sckott opened 8 months ago

sckott commented 8 months ago

blockers/pre-reqs

[ ] should it go to cran? if not, close this
[ ] currently depending on a dev version of package vcr that Scott maintains. can not submit a package to cran that depends on a package that is not on CRAN, Bioconductor or a CRAN like repository
[ ] make changes that will smooth a cran submission:
- they want some egs to actually run, give em some even if dummy egs
- make sure no tests will run that may break
- run url checker
- run checks on r-hub and winbuilder

tefirman commented 2 months ago

Love this idea, definitely think it belongs in CRAN! I don't see this package changing much in v2.0, so I wonder if this is worth doing before v2.0? Unfortunately, the effort for submission seems kinda high, so I set it as v2.0, but I'm open to moving it to v1.X if people feel strongly about it.

sckott commented 2 months ago

Thanks Taylor. There's one kinda big thing to think about though wrt cran and this pkg. If we move away from Shiny for the proof front-end, then we won't be dog-fooding this package and proofr anymore; and if we're not dog-fooding these pkgs anymore, do we keep maintaining them (the best tools seem to be made by people that use them themselves; e.g., githubbers use github to build github)? Maybe FH users will still use these R packages even if we aren't using them? But maybe not. TLDR: I think hold off on CRAN for now