Plan tidyverse team issue labelling extravaganza

[hadley]

So that we have 100-200 issues labelled with tidy-dev-day

Includes creating documentation issues.

Existing issues: https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Atidyverse+org%3Atidymodels+org%3Ar-lib+archived%3Afalse+label%3A%22tidy-dev-day+%3Anerd_face%3A%22+

[hadley]

Brain dump of a few ideas:

• Convert haven to use S7
• Convert blob to use S7
• For all tidyverse packages, check there's a link to the getting started vignette from the readme (like README should end with link to getting started vignette rvest#410)
• Review all existing upkeep issues as potential TDD candidates
• Consider if any usethis issues could be manually applied to tidyverse/r-lib packages
  • Run pkgdown::build_articles() and add missing alt text
  • Update Rmd chunk style
  • Eliminate mockr/mockery
  • Replace expect_error() with expect_snapshot()
• Stuff we can now do since we rely on R 4.0.0
  • Drop stringsAsFactors
  • Drop rappdirs in favour of R_user_dir() etc
  • Look for deparse1() potential usage
• If you know a language other than https://pkgdown.r-lib.org/articles/pkgdown.html#language, add a pkgdown translation
• Pick a package (forcats?), set it up with tr_() and then get folks to provide translations
• Convert examples to use base pipe.

[georgestagg]

Some more ideas:

• Add an “Investigate” tag for issues that need looking at more.

• Add “Create a reprex” tags for issues that need examples

• Convert package to use {cli}

  • https://cli.r-lib.org/reference/inline-markup.html
  • https://usethis.r-lib.org/dev/articles/ui-cli-conversion.html
  • Example: {rsample}'s {cli} epic: Use cli errors tidymodels/rsample#457

• Packages that have fallen behind on upkeep

• Potentially add error chaining, where it's helpful and reasonably easy for a newbie

• Issues in documentation and/or roxygen markup

• Issues in the R4DS & R packages books, potentially others

• Changes required to follow tidy style

  • https://style.tidyverse.org/index.html

[jennybc]

Another idea that would lead to issues in multiple repos:

r-lib/usethis#1923

• Locate all packages that still use s3_register()
• For each package, analyse why we're using it and suggest what actions someone needs to take

[hadley]

Done! https://github.com/issues?q=is%3Aopen+is%3Aissue+archived%3Afalse+label%3A%22tidy-dev-day+%3Anerd_face%3A%22 — 265 issues as of today.