Community
Community
Ultraviolet is built in public. Questions, bug reports, handbook review, docs fixes, and code contributions all happen in the open — no money required.
Find the right venue.
Everything happens on GitHub — pick the door that matches what you came to do.
Ask a question
GitHub Discussions. Share what you are building and propose ideas before opening large changes.
Open Discussions →Report a bug
Issue tracker. Compiler, runtime, toolchain, handbook, and documentation problems against the alpha.
Open Issues →Read the source
Language repository. Compiler, runtime, uv tool, handbook, and conformance material — all public, Apache-2.0.
Browse the repo →Highest-leverage contributions first.
During the alpha, these four things move the project most — in this order.
Test the alpha on your platform
Run the installer or build from source, then report exactly what breaks. Install and build reports across platforms are the highest-leverage contribution right now.
Get the installer → 02Review the handbook
The handbook is the source of truth. Ambiguities, contradictions, and unclear judgments are bugs — file them like any other defect.
Read the handbook → 03Improve docs and examples
Docs gaps, broken walkthroughs, and missing examples block adopters before the compiler does.
Open pull requests → 04Evaluate AI-written Ultraviolet
Generate Ultraviolet with your preferred model, audit it against the review model, and share findings.
Read the review model →