There's a lot of PRs backed up, and a really interested community. That can be a bit tricky as an open source maintainer when pressed for time.

Previously: #264 discussed a bit of these things

Starting a general discussion for ideas around how contributions can be of a high quality and generally safe to merge, or how others can help with triage, etc.

Things that have worked in previous projects for me:

Flip to github org + teams?

Risk: HACS links break?

• https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch
• https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams
• https://www.cloudsavvyit.com/14568/how-to-transfer-a-github-repository-to-your-organization-or-another-user/

Maybe - 3x good PRs, bump up people to a contributor status?

A dev vs mainline branch, with core contributors controlling releases, but casual contributors able to merge to Dev?

More templates and automation

• Test coverage or test results as a requirement for merging?
• automated code lints
• tagging and auto close bots for stale tickets? https://github.com/apps/stale
• Create pull_request_template.md #782
• Create CONTRIBUTING.md [ci skip] #783

When is this closable?

Recommend closing this if a few of the PRs seem useful and are adopted; or if it sits with no activity for ~3 months.