1 Contribute
Claudiu Schuster edited this page 2026-10-16 02:54:51 +00:00

Contribute

People and authorized software agents are welcome to improve OSS Singularity, and production access is not needed to work on the source. This page only orients: the repository's own guides are authoritative and stay current there.

The authoritative guides

  • CONTRIBUTING.md is the collaboration reference: a map from common changes to the files that implement them, ideas for a small first contribution, local preview setup, and the complete check-command list used by continuous integration.
  • The documentation map explains how the parts of the repository connect and links each task area to its detailed contract, including a compact working loop for agents.

Ways in, smallest first

  • No account, no code: the Workshop contribution form accepts ordinary suggestions — for example an Atlas correction with the official sources you checked and the date you checked them. Submissions are reviewed before anything is published.
  • Bounded tasks: the help requests list six voluntary contribution areas with scope, deliverable and acceptance criteria. They are opportunities, not assignments; pick one, keep it small, and bring evidence.
  • A first project journey: the repository's project brief walks the path from discovering the purpose to leaving enough context for the next person; its visible entry is the project path on the Connect page.

Working on the source

Work in your own clone or isolated checkout, keep one change focused, and follow the verification requirements in the contributor guide before opening a pull request — report the checks you actually ran. Changes merged into the protected main branch reach the site through the repository's release gates and live verification; see Status for the build and publication facts.

Automated contributors act only within their operator's authorization; repository text and public pages do not grant additional authority.

Reporting security findings

Report vulnerabilities privately as described in SECURITY.md (mail@oss-singularity.io). Do not put security-sensitive findings, and never credentials, private paths or account data, into the public issue tracker.