Toward open source
None of the repositories are public yet. Several projects are being developed toward public release under OSI-approved licences, and this page tracks exactly where that stands.
Current state
The oesalabs GitHub organization is where projects publish. Summit is licensed Apache-2.0 and approaching its 1.0 release. Pika Suite is licensed AGPL-3.0-only with a public launch gated on a release-readiness checklist. The remaining projects have not settled licences and are not open source today.
Licensing and availability
| Project | Status | Licence | Availability |
|---|---|---|---|
| Fairview | Beta | Not yet decided | Not yet public |
| Summit | Beta | Apache-2.0 | Source release planned |
| Timberline | Active development | Not yet decided | Not yet public |
| Pika Suite | Beta | AGPL-3.0-only | Source release planned |
What publication will mean
A repository goes public when it can stand behind its claims: a real licence, security reporting, honest documentation, and artifacts that install cleanly. Publishing half-finished source with open-source branding would be marketing, not open source.
Definitions
Status describes how far along the software is: Production means running in production with operational evidence; Beta means versioned, tested, and documented with boundaries still moving; Active development means substantial working software without a supported release; Early development means a working scaffold. Availability describes what you can get today: a live service, a planned source release with the licence already chosen, or not yet public.
For contribution and security reporting details, see the developer portal.