@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
@koen_hufkens thank you! Good to know! We're still a little way off going 'live' with the package but this is all super useful info
@joechip90
rOpenSci IMO is exactly aimed at these kinds of cases where support is hard, but it leans on the assumption that there is a sufficiently large pool of maintainers to pick up any slack.
My post questions the latter, especially if intrinsic motivation is lacking and/or erodes over time.
I would encourage people to go the rOpenSci route, for code review but consider the above caveats.