Todo_rOpenSci.md

In ClaudioZandonella/PRDAbeta: Conduct a Prospective or Retrospective Design Analysis

Todo rOpenSci Packages

• [x] You can choose to use = over <- as long you are consistent with one choice within your package.
• [x] README should include: https://devguide.ropensci.org/building.html#readme
• [x] We recommend not creating README.md directly, but from a README.Rmd file (an R Markdown file) if you have any demonstration code. (usethis::use_readme_rmd())
• [x] Add #' @noRd to internal functions.
• [x] Only use package startup messages when necessary (function masking for instance). Avoid package startup messages like “This is foobar 2.4-0” or citation guidance because they can be annoying to the user. Rely on documentation for such guidance.
• [x] https://devguide.ropensci.org/building.html#website
• [x] Use Imports instead of Depends for packages providing functions
• [x] use the goodpractice package (goodpractice::gp()) as a guide to improve your package, since most exceptions to it will need to be justified
• [x] Test coverage below 75% will likely require additional tests or explanation before being sent for review. Once you’ve set up CI, use your package’s code coverage report (cf this section of our book) to identify untested lines, and to add further tests. usethis::use_coverage()
• [x] Both test status and code coverage should be reported via badges in your package README.
• [x] R packages should have CI for all platforms when they contain Compiled code
• [x] https://devguide.ropensci.org/ci.html continuos integration
• [x] We urge package maintainers to make sure they are receiving GitHub notifications, as well as making sure emails from rOpenSci staff and CRAN maintainers are not going to their spam box.
• [x] If you would like your package to also be submitted to Journal of Open-Source Software (JOSS), it should include a paper.md file describing the package. More detail on JOSS’s requirements can be found at their website. https://joss.theoj.org/about#author_guidelines
• [x] use repostatus.org badges (which we recommend) https://www.repostatus.org/
• [ ] name function object_action()

send

• [ ] Next, open a new issue in the software review repository and fill out the template. https://github.com/ropensci/software-review/issues/new

other:

• [x] problema del welch's t test e correzione d di cohen
• [ ] change name repo and package
• [x] Add more description on hypothetical effect size in vignette overwie and readme
• [ ] Update Zenodo
• [ ] Updarte URL in DESCRIPTION
• [ ] Coverage for multiple CI (https://devguide.ropensci.org/ci.html#coverage)
• [ ] Problem with .covrignore function RcppArmadillo
• [x] Fail CI on windows

Changed name

• [ ] url in DESCRIPTION
• [ ] url in readme
• [ ] zenodo
• [ ] url in paper
• [ ] url in vignette PRDA

Joss:

• [ ] https://joss.readthedocs.io/en/latest/submitting.html

After submission:

• [ ] Once you have submitted a package and it has passed editor checks, add a peer-review badge via... (https://devguide.ropensci.org/building.html#readme)
• [ ] After a package is accepted but before transfer, the rOpenSci footer should be added to the bottom of the README file with the following markdown line... (https://devguide.ropensci.org/building.html#readme)
• [ ] After transfer to our GitHub organization, rOpenSci Code of Conduct will apply to your project. Please add this text to the README (https://devguide.ropensci.org/collaboration.html#friendlyfiles)

ClaudioZandonella/PRDAbeta documentation built on Sept. 23, 2020, 8:51 p.m.