Contributing

We are preparing for an eventual open source release. These guidelines are a local draft for invited collaborators; they do not grant access, publish code, or offer a license.

Before you start

Read the repository README and Code of conduct. Agree on the problem and acceptance criteria with a maintainer before undertaking a large change. Use the relevant repository's documented setup commands; ask if they are missing. Do not infer production readiness from a local test result.

A useful change

1. Work on a focused branch, not directly on the default branch.
2. Explain the problem, proposed behavior, and any compatibility or security implications.
3. Add or update tests and documentation. Run the repository's documented checks and report exact commands and outcomes, including skipped checks.
4. Open a pull request with a small, reviewable diff. Include a rollback approach where behavior changes.
5. Wait for maintainer review. Publishing, deploying, changing verification policy, and releasing funds are separate approvals, not consequences of a merged patch.

Never commit secrets, personal data, production dumps, or unredacted logs. Do not enable Verified or represent compute or allocation checks as proof of hardware residency. Follow Security policy for suspected vulnerabilities.

Contribution rights — decision pending

We recommend the Developer Certificate of Origin (DCO) rather than a separate contributor license agreement. This is a proposal, not an active submission requirement. If adopted at launch, contributors must review https://developercertificate.org/ and use git commit -s only when they can truthfully certify the contribution. A sign-off is not a cryptographic commit signature.

No license is applied by this document. See License recommendation. Questions: hello@omegacompute.com.