Hmm, I always thought of ROpenSci as a curator or like a “journal”. You bring them a package, they determine if it’s a good fit, then it gets a peer-review process and becomes an ROpenSci package. I’m not sure how that would interact with another organization… But maybe I misunderstand what they do.
I’ve reviewed for them. I’m not sure what a proper production review entails. I followed a checklist of typical concerns, read over and ran every line of code, suggested refactorings and improvements to unit tests and documentation, and wrote up my findings like an article review. It was actually pretty extensive. It might depend on the reviewer too though.