Developers
Contribution routes
Contributions can be code, tests, specifications, documentation, issue triage, tutorials, interoperability results or real deployment requirements.
What you’ll do
Contributions can be code, tests, specifications, documentation, issue triage, tutorials, interoperability results or real deployment requirements. The most effective route matches a defined need with a maintainer and review process.
Before opening a large pull request, show the proposed change to the maintainers and agree what success looks like. A small reproducer, failing test, design note or documentation correction is often the fastest way to establish shared context and reduce review effort.
Before you begin
A clear contribution path turns interest into maintained ecosystem capacity rather than a one-off prototype.
Steps
1. Project route
Fix or extend a specific repository using its issue tracker, licence and review rules.
2. Working-group route
Address a cross-project topic such as portability, SoC integration, language behaviour or standards alignment.
3. Evidence route
Publish reproducible measurements, porting notes or assurance findings with enough context for others to use.
Check your result
Before contributing employer-owned work, confirm intellectual-property, licensing, confidentiality and export-control obligations.
Record the architecture, platform, ABI, release, source revision and complete commands. A second developer should be able to reproduce the result.