Noam Ross

Big fan of this - we do a bunch of qualitative coding on both scientific literature and semi-structured interviews. We work with MAXQDA but its outputs don't fit super easily...

One possibility is to build this as a wrapper/plugin for [**goodpractice**](https://github.com/MangoTheCat/goodpractice). At last year's unconference Gabor created a plug-in structure and Hannah Frick has been working on extending and [documenting](https://mangothecat.github.io/goodpractice/articles/goodpractice.html)...

Just bookmarking this: we had a conversation a bit ago with an organization interested in our review process. It wasn't public, but they asked good questions about initiating the process,...

And, many might have already seen these, but some relevant posts: - https://ropensci.org/blog/2016/03/28/software-review/ - https://ropensci.org/blog/2017/09/01/nf-softwarereview/ @goldingn we feel you, building and maintaining the reviewer base is one of the biggest...

Expanding `pkgreviewer` and`PackageReviewR`, and perhaps integrating them, might be a full-blown unconf project if folks want to take it up.

I've been working on a tool to create a package diagnostic report. I had originally thought of it as giving a quick scan for us rOpenSci editors to use, and...

If the Python version is performance, it might be worthwhile to try to wrap it with the **reticulate** package rather than port it. With **reticulate** you can share in-memory objects...

This is a hard problem! I have an as-yet unfunded proposal to develop a system that tries to use text-recognition ML identify fields in a dataset and link them to...

What about incorporating something like https://github.com/ropenscilabs/packagemetrics to the information returned, so that when searching for a package you get not only a description, but indicators of popularity and quality?

It occurs to me that some of this work would be applicable to the editorial need of finding _authors_. For instance, given a package submission, could we identify packages with...