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]

Assigning to @georgestagg

[georgestagg]

I'll need an admin to add me to the tidyverse org so I can edit Issue labels.

[hadley]

@georgestagg FWIW you shouldn't need to add labels; your job is to make other people label issues 😄

[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 https://github.com/tidyverse/rvest/issues/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.