Thanks for helping. Raze values correctness, reproducibility and measured performance over feature count.
- Open an issue first for anything larger than a small fix.
- Work on a branch; keep commits focused and use conventional prefixes
(
feat(r6):,fix(rix):,perf(kernel):,docs:,test(iso):). - Before opening a pull request:
nix develop -c cargo fmt --all --check nix develop -c cargo clippy --workspace --all-targets -- -D warnings nix develop -c cargo test --workspace nix build .#checks.x86_64-linux.core-boot .#checks.x86_64-linux.desktop
- Performance claims need numbers: describe the method, the hardware or VM, and
include before/after measurements (see
docs/performance/methodology.md). - Do not describe delegated or upstream functionality as native Raze work.
See docs/development for building and testing details.