With the increased use of LLM, it's much easier to submit packages faster than they could be submitted previously. Further, maintainers can create more packages more quickly, but they still do need to maintain them.

To protect our volunteer peer review team, it makes sense to ensure that maintainers only submit a single package at a time. A new package can't be submitted until the first one has undergone a complete review. We might want to consider an edge case if two maintainers work on the same two packages - one at a time should always be the default.

Let's add language regarding the volume of submissions to pyOpenSci to our policies guide here:

https://www.pyopensci.org/software-peer-review/our-process/policies.html

We should also reference these poliicies - and this one specifically via a link in the author guide
https://www.pyopensci.org/software-peer-review/how-to/author-guide.html#

Following @hamogu's comment, we should also consider an edge case where there are two closely related instances (we haven’t seen this yet, Moritz, so we will need your guidance on that use case). There may be a case for reviewing them together by the same editor. Let's ensure we get feedback from Moritz on this to ensure we craft it correctly once a PR is open!

@eliotwrobson tagging you on this as active peer review lead!