People running successful open source projects: what do you do when the rate of PRs grows beyond what you can handle? How do you ensure that PRs have had at least one collaborator respond, without being drowned in notifications/emails yourself?
Please RT for reach.
@wilfredh deputies. If your scale is over that which one person can reasonably do, start mentoring, which will slow you down elsewhere, but in the long term will increase capacity.
@wilfredh The first thing is set expectations. You can add something to the PR template or just have a boilerplate comment, but tell people how long they may have to wait to have it reviewed and anything they can do to make it easier for you. After that, create a triage system (kanban or tags) so it’s easy to search for what PRs are unassigned, then schedule a regular triage time. You can rotate those responsibilities too. Then it’s safe to turn off notifications because you have a process.
@audrey Great suggestions, thank you! Do you have any favourite tools for tracking tags or maintaining kanban state from GitHub?
@wilfredh Right now I’m using github’s project feature with the built-in automation, but I might switch to airtable https://zapier.com/apps/airtable/integrations/github
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!