Start by writing contributor-friendly docs: quick start, architecture overview, and triage labels. Provide runnable examples so newcomers can reproduce issues quickly.
Use issue and PR templates to guide reports and proposals. Acknowledge contributors, even for small fixes—gratitude encourages future participation.
Batch releases with changelogs and upgrade guides. Keep breaking changes rare and well-documented to respect downstream users.
Protect your time: schedule support windows and automate routine responses. Healthy boundaries make maintainership sustainable.