get involved
Contribute
The reciprocal loop only works if people push back. Stress-test the code, audit it for leaks, break it on hardware nobody planned for, then send the fix upstream. This page is the practical on-ramp.
How to actually contribute
Pick a project
Everything lives under the GitHub org: github.com/uncoalesced. Each repo's issue tracker is the single source of truth for open work.
File issues in the open
Bug reports, hardware edge cases, performance regressions, and audit findings all go through the public issue tracker, with steps to reproduce and details of your setup. No private triage channels.
Send changes upstream
Pull requests are reviewed against the submission standards below. Patches are merged in public and versioned clearly, so your contribution stays on the record.
Submission standards
Every contribution is held to the same standard as the core. That's what keeps independent pieces working together.
Zero unnecessary dependencies
Reach for core language primitives before third-party packages. If a dependency can be replaced by a hundred lines of clear, owned code, replace it. Every import you add is something a future auditor has to trust.
Determinism & thread safety
Isolate threads explicitly and make behavior under load predictable. A contribution that works on your machine but races under extreme concurrency is not done. Heavy concurrency is exactly what this code gets tested against.
Complete documentation
Document the architecture, not just the API: performance trade-offs, memory layouts, and why the design is shaped the way it is. If your PR changes behavior, it changes the docs too.
Security disclosures & code inspections
Security research happens in the open. Vulnerability reports, memory leak discoveries, and concurrency issues are logged via public issue trackers, with patches merged transparently and versioned clearly. There is no black-box disclosure process: finding problems in this code, out in the open, counts as a real contribution.