Ranex

Contribute / four ways to help

Help put the judge to the test.

Run the kernel, report a failure with steps to reproduce it, or help close a known gap. Ranex is open source. Useful contributions start with something we can check.

01

Run the kernel

Follow the source-run quickstart and keep the report from the included demonstration. Compare the evidence with the verdict.

Get started →

02

Report a reproducible failure

Include the command, version, expected result and actual output. The free bug report template gives you a place to collect them.

Prepare a bug report →

03

Work on a known gap

Read the current boundaries before proposing a change. Open an issue in the kernel repository to discuss the expected behavior and how to test it.

Read the known limits →

04

Discuss a pilot

Tell us about your repository, review process and a failure you want the acceptance gate to catch. That gives us a concrete starting point for a conversation.

Talk about your workflow →

Field notes

Follow the work as it happens.

Get notes about the checks, the failures and what changed in the kernel. This is an email subscription. To discuss a pilot, use the contact page above.

Subscribe to the field notes ↗