Hi everyone, The Spark community is full of talented people eager to give back, but navigating the onboarding process effectively often requires an "insider" connection or significant internal guidance.
To make the project more accessible and sustainable without overburdening our current maintainers, I propose we establish a structured onboarding and sponsorship process. *How it could work:* 1. *AI-Assisted Triage (First Review):* We could integrate an AI assistant/bot to act as the initial "mentor" and reviewer for new contributors. This AI would handle basic linting, style checks, verifying unit tests are included, and answering common setup questions; we can add more complex logic to the AI assistant with time. This ensures contributors get instant feedback and fixes basic issues before a human ever looks at the code. 2. *Community Sponsorship Balance:* Once a PR passes the initial AI triage, the contributor is paired with a human sponsor. To scale this, we could introduce a community expectation: frequent contributors who regularly submit PRs help sponsor/mentor a newcomer. This reinforces the idea that nurturing the community and reviewing peer code is just as vital to Spark's success as adding new features. It offloads the initial noise from core maintainers while building a stronger, more self-sustaining reviewer base. I’d love to hear the community's thoughts on this approach, particularly around ways we can help newcomers. Thanks, Nimrod
