-
Notifications
You must be signed in to change notification settings - Fork 12
Promoting link-y-ness in R packages: GitHub links #41
Comments
Sounds like fun! |
@HenrikBengtsson also replied with a related idea: that packages developed on GitHub should include a link back to their CRAN page, by default as the main URL for the repo or elsewhere in the README. |
Linking back to CRAN seems mostly nicely done with a CRAN badge; I wonder if there's other badges that a bot could automatically suggest. |
I didn't know there were two packages for badge creation: There are badges with the version number for the devel/released version. |
There's also https://www.r-pkg.org/services#badges |
There are so many badge creation services but none are particularly satisfactory. Maybe we can have a brief discussion/hack session around improving existing packages (as PRs). CI status: x, y, z or something like that. |
This would be really cool to work on. The first time I created badges, I copypasta'd from other people's repos (which, btw, is such a nice feature of working on open source), but it would be nice to automate that, with some control, like @karthik suggested. |
Specific issue for badges #58 |
@karthik I found that I used my own package badgecreatr mostly without the main function to dump all the badges at once and mostly used the separate badge-create-functions. I definitely welcome ideas, and PR's, to improve everyone's workflow. |
I find it so helpful, once I fall down some rabbit hole, to find that my rabbit hole has been equipped with all the links I am likely to need.
Concrete Unconf project idea is something I tweeted:
Create a bot (or script?) that makes a PR to R pkgs that are developed on GitHub but lack said link(s) in DESCRIPTION.
There are lots of details to be worked out but I think this work would have immediate and lasting value. It also gives a great opportunity to work with the GitHub API (maybe via gh?), rOpenSci's git2r package, and the services offered by @gaborcsardi via METACRAN (specifically the API re: R packages and the GitHub read-only mirror of all CRAN packages).
The text was updated successfully, but these errors were encountered: