Build with us.
We welcome thoughtful contributions to our software, documentation, and public infrastructure. Start with the repository that owns the work, and talk with us before investing significant time in a large change.
Small fixes can start small. Large changes should start with scope.
Small, self-contained fixes may be proposed directly where the affected repository's guidance permits. For a large change, new dependency, architectural change, or public-interface change, open an issue first so the scope can be discussed before substantial work begins.
Acceptance is selective and evidence-based.
We may accept, decline, request changes to, or defer proposed work based on factors including:
- fit with current repository scope and needs;
- technical or editorial merit and appropriate evidence;
- maintainability and consistency with architecture and standards;
- security and operational risk;
- licensing and third-party provenance;
- governance alignment;
- review capacity and long-term maintenance cost.
Meeting one factor does not guarantee acceptance.
Review and merge are separate gates.
External copyrightable contributions may be opened and reviewed, but they are not merged until the applicable contributor-agreement requirement is satisfied.
The full policy and Code of Conduct below are maintained on GitHub.
Find the repository that owns the work.
Repository-specific setup, architecture, and technical requirements stay with the repository itself. If you are unsure where an idea belongs, ask before investing significant time.
The organization guidance and repository list below open on GitHub.