We welcome new contributors.
Many open source journeys begin with curiosity, a small improvement idea, or an AI assistant helping prototype a change. We are supportive of that energy.
At the same time, we are building a long-term ecosystem. Sustainability, alignment, and code quality matter just as much as velocity.
This document explains how to turn a first contribution into lasting impact.
Turn this:
Random idea → random PR
Into this:
Curious builder → aligned contributor → long-term collaborator
Code is abundant. Attention and alignment are scarce.
We optimize for signal, clarity, and sustainability.
Open source can feel opaque from the outside.
If you're new to this project — or to open source in general:
There are no hidden rules here. If something feels unclear, ask.
We are building in the open.
If you’re new here, we recommend starting with:
good first issueFor non-trivial features or architectural changes:
Early discussion dramatically increases the likelihood your work will be merged.
Open source has longer feedback loops than internal teams.
We are an active project and we review frequently, but maintainers have other responsibilities. You should expect:
If a PR has not received attention after a reasonable amount of time, a polite comment is welcome.
Please avoid opening multiple PRs to get attention faster. Focused, well-explained contributions get reviewed sooner.
A strong contribution:
A good PR reduces cognitive load for reviewers.
We are supportive of AI-assisted development. This document itself was written with AI assistance.
Many contributors — including maintainers — use AI tools as part of their workflow. We see AI as a normal part of modern software development.
AI is a tool. Responsibility remains human.
You must understand the code you submit, be able to explain your design decisions, and ensure correctness, performance, and licensing compliance.
AI should raise quality, not just increase output.
Large or surprising PRs are harder to merge than discussed ones.
Before introducing:
Open an issue and discuss the approach.
Alignment saves time on both sides.
To protect review bandwidth:
For new contributors, we recommend having one open PR at a time until your first contribution is merged.
This helps maintain focus and ensures meaningful feedback.
Every project has boundaries.
We may decline contributions that:
This is about sustainability, not gatekeeping.
We value:
Community health is as important as merged code.
As trust builds, so does responsibility.
Contributors naturally grow from:
Over time:
Open source is a relationship, not a transaction.
AI makes writing code easier.
Building a healthy ecosystem still requires:
If you are here to build something meaningful, participate in the conversation, and grow with the community, we are excited to work with you.