Jim Hester

It would be nice to have some conventions around intermediate level issues motivated people could take on as well. There have been times where I wanted to contribute to a...

- [x] Search packages on GitHub http://rpkg.gepuro.net/download, This also has R-forge due to Jeroen's R-forge mirror. - [ ] Search abbreviations - https://github.com/jimhester/available/issues/3 - [ ] Regular dictionaries - https://www.programmableweb.com/category/dictionary/api...

https://github.com/ropensci/unconf17/issues/56 is the same thing, codecov.io is going to be getting a plugin system in the not too distant future, so I am planning on using it to do this,...

https://romain.rbind.io/blog/2017/05/14/calling-go-from-r/ is relevant to this, however the problem in my mind isn't how you call the go shared library from R but how you distribute the package. CRAN is not...

Rperform seems like it already does most of this, but clearly needs more exposure / use and possibly some thought into better integration into pkgdown / travis so it is...

I don't know of anything like codecov.io for tracking benchmarking over time. If there was something we could use it or maybe setup a simple service to do so.

> your license covers what you distribute. Since you're not usually distributing any part (source or binary) of these dependencies, you're not governed by their licenses. > package license only...

I think the current CRAN badge should maybe be changed to automatically show the CRAN check status. Mainly so package author's know when it is broken on CRAN, since I...

@gaborcsardi, probably true, but CRAN doesn't do that currently. Back on topic a badge for the number of required package dependencies (`Imports` and `Depends`) could be useful.

One thing you can do is have a badge for example and vignette coverage, see also https://github.com/ropensci/unconf17/issues/2