005 First pass at org combination proposal #13
Conversation
hadley
changed the title
Co-authored-by: Jim Hester <james.f.hester@gmail.com>
005-github-simplification.Rmd
Outdated
| - There are a few packages that I am confused about: | ||
|
|
||
| - Is rvest programming or data science? what about httr? | ||
| - usethie is technically programming, it's very user facing, and we expect data scientists might use it for analysis projects. |
There was a problem hiding this comment.
| - usethie is technically programming, it's very user facing, and we expect data scientists might use it for analysis projects. | |
| - usethis is technically programming, it's very user facing, and we expect data scientists might use it for analysis projects. |
005-github-simplification.Rmd
Outdated
|
|
||
| Cons: | ||
|
|
||
| - Makes it more complicated to explain exactly what the tidyverse is: it's a package, it's a set of packages loaded by `library(tidyverse)`, it's a set of packages installed by `install.packages("tidyverse")`, **and** it's a GitHub organisation. |
There was a problem hiding this comment.
So, when you say "tidyverse org" you mean tidyverse as-is (not a renaming to tidyverse-org, or something of the like)?
005-github-simplification.Rmd
Outdated
| ## Open questions | ||
|
|
||
| - GitHub's existing forwarding should handle most cases, but there a few cases where you'll need to update the urls in the GitHub repo. But are there any existing workflows that this would break? | ||
| - Should we consider the moving the websites as part of this process? If so, how do we manage the redirects? Will need to set up some external server. |
There was a problem hiding this comment.
I think if repos are moving between orgs, it would be good to move the websites as part of the same phase, as opposed to a 2nd phase. It seems confusing to me to (e.g.) have vroom.r-lib.org as the URL but the repo is tidyverse/vroom or rstudio/vroom. I think it would be additionally confusing if this will change in a short-ish time span.
|
Possible ideas for promoting the visibility of more 'user facing' packages, so new users are not overwhelmed by 'all the packages in the tidyverse'
If it is important to make the distinction between, 'this is installed explicitly by the tidyverse package' and this is an infrastructure package that might be used by a tidyverse package is important we can have tags and badges for them appropriately. |
|
I think we would want to use something other than "core-tidyverse" since that label is used for the eight packages explicitly loaded with |
Yeah, there's been quite a bit of discussion re. what core vs. non-core means for tidyverse packages: |
|
I was talking about just the 8 packages listed on the website. |
Co-authored-by: Lionel Henry <lionel.hry@gmail.com> Co-authored-by: Mara Averick <maraaverick@gmail.com>
And re-build
No description provided.