Improve the code
Start with a focused change, explain its boundary and include tests that make the intended behavior visible.
BUILD TOGETHER
Bring a better idea.
Help make it real.
Good foundations grow through focused contributions: useful code, clear documentation, reproducible tests and practical requirements.
CONTRIBUTION PATHS
More than one way to contribute.
Test a real scenario
Record the exact assembly, environment, steps and observed result. Distinguish a passing build from a running, verified capability.
Clarify the docs
Help remove conflicting status statements and keep examples aligned with the release they describe.
Bring a requirement
Explain the job your team needs to do before proposing a subsystem. A concrete workflow makes design tradeoffs easier to evaluate.
A useful issue starts with evidence.
For a non-sensitive bug, prepare the release or commit, storage aggregate, relevant configuration with secrets removed, exact reproduction steps, expected behavior and observed behavior. Include a minimal example rather than private content or a complete production repository.
For a design proposal, state which capability is missing, who needs it, what is out of scope and how you would verify it. Call out whether the proposal depends on the unimplemented lifecycle layer.
Keep security reports private.
Do not include credentials, personal data or exploit details in public issue material. The security page must provide a verified private reporting route before the public contribution workflow opens.
Start by understanding the foundation.
A contribution has more value when its assumptions are visible.