Read the source
Inspect the compiler, examples, design archive and current implementation notes.
Open GitHub ↗Community
Build the language
in public.
Ostrin is early, open source and technically focused. The best way to participate today is to inspect the code, reproduce a behavior, improve an example or propose a precise language decision.
Start here
Choose a concrete way to help.
Each path points to a real repository surface. There is no invented chat or external community program to join yet.
Report a reproducible issue
Use the issue templates to include source, command, platform, expected behavior and actual output.
Open issue templates ↗Make a first contribution
Documentation, examples, website checks and diagnostics are useful entry points before changing the type checker.
Read contributing guide ↗Understand the rules
Language proposals should explain syntax, semantics, runtime impact and how the behavior will be tested.
Read design archive ↗Build something public
External projects that use .ostrin help test the language in the wild and build the evidence needed for a future GitHub Linguist proposal.
Copy the starter kit ↗Project guardrails
Technical focus keeps the community useful.
The repository has a code of conduct, a test-first contribution path and an honest roadmap. Community tooling should make those norms easier to follow, not pretend the project is larger than it is.
Evidence with every change
Relevant design decisions, positive and negative examples, tests, documentation and known limitations belong in a pull request.
Read the guide ↗Respectful disagreement
Critique ideas and code with patience, focus and evidence. Harassment, threats and deliberate disruption are not acceptable.
Read the code ↗See what is real
Available, in-development and future work stay visibly separated so contributors can choose the right level of commitment.
Open the roadmap ↗Public projects
Show what you build.
Public experiments, packages and scientific examples help test Ostrin in real settings. Use the showcase template with a link, reproduction command, expected result and license.
Submit a public project ↗- Good first contribution guidance is in the repository
- Bug, feature, language, package and showcase templates are prepared
- Recommended labels are documented ↗
- External usage is counted separately for the Linguist path