CurrentCommunity · Guide
Contribute to Mobazha
Send a documentation, client, Node, website, RFC, or policy contribution to the repository that owns it.
Choose the owning repositoryEstimated time5 minutes
Trust, applicability, and sourcesCurrent public project policy or service surface
Choose the repository
- Node business logic, deployment, public APIs, extensions, conformance, and release evidence: mobazha/mobazha.
- Buyer, seller, responsive UI, and runtime-capability client behavior: mobazha/mobazha-unified.
- Brand website, pricing, service terms, and public marketing: mobazha/mobazha.org.
- Project-wide public policy, task guidance, cross-repository explanation, Agent discovery, and documentation quality: mobazha/mobazha-docs.
Contribution contract
- Open an issue or discussion before a large architecture, protocol, payment, security, or governance change.
- Keep the change focused and update tests, schemas, docs, migration guidance, and release notes together.
- Do not include credentials, private endpoints, customer data, proprietary code, or generated release binaries.
- Use DCO sign-off for source contributions where required by the owning repository.
- Report vulnerabilities privately rather than through a public pull request or issue.