This is an automated archive made by the Lemmit Bot.

The original was posted on /r/opensource by /u/readilyaching on 2025-12-15 15:10:49+00:00.

Iā€™m looking for advice from people whoā€™ve been in this situation before.

I maintain an open-source project thatā€™s started getting a solid amount of traction. Thatā€™s great, but it also means a steady stream of pull requests (8 in the last 2 days), issues, questions, and review work. Until recently, my brother helped co-maintain it, but heā€™s now working full-time and running a side hustle, so open source time is basically gone for him. That leaves me solo.

I want community contributions, but Iā€™m struggling with reviewing PRs fast enough, keeping issues moving without burning out, deciding who (if anyone) to trust with extra permissions (not wanting to hand repo access to a random person I barely know).

Iā€™m especially nervous about the ā€œjust add more maintainersā€ advice. Once permissions are granted, itā€™s not trivial (socially or practically) to walk that back if things go wrong.

So Iā€™d really appreciate hearing:

How do you triage PRs/issues when volume increases?

What permissions do you give first (triage, review, write)?

How do you evaluate someone before trusting them?

Any rules, automation, or workflows that saved your sanity?

Or did you decide to stay solo and just slow things down?

Iā€™m not looking for a silver bullet, just real-world strategies that actually worked for you.

Thanks for reading this far, most people just ghost these.ā¤ļø

Edit: Thank you all for being so helpful and providing me with the information and support that you have. This postā€™s comments section is the dream I have for Img2Num, and I will never stop chasing it until I catch it.