AURORA IN DEVELOPMENT

COMMUNITY / CONTRIBUTING

Contribute with evidence.

Contributions should improve correctness, clarity, accessibility or maintainability. Product claims must remain traceable to reviewed evidence.

AURORA / PUBLIC INFORMATION / EN

Start here

  1. Read the repository README and architecture decision records.
  2. Check existing issues and pull requests before starting overlapping work.
  3. Describe the problem and expected behavior before proposing a broad refactor.
  4. Keep changes focused and avoid unrelated dependencies.
  5. Run project checks and review the rendered result.

Repository access

The public contribution workflow currently applies to the Aurora Website repository. The Aurora OS repository is private, so direct public contributions to the OS source are not currently available through this site.

Content contributions

When proposing a product status change, include the exact source, test or report that supports it, the revision tested and any limitations. Do not turn a planned architecture into an implemented feature claim.

Open GitHub repository ↗