@koen_hufkens thanks for your thoughts here! I havent run packages through ROpenSci before but now I'm back from paternity leave we're getting close to the release of a package that we were planning to run through them. However, with funding cycles in research being what they are, then none of the current developers can commit to constant maintenance. Updates to a package are likely to be a stop-start with fewer and more intermittent but large updates. It sounds like this maintenance model might be fundamentally incompatible with ROpenSci requirements