Open source
Build in the open. Ship with radical clarity.
OpenStudio uses GitHub as its public engineering surface: repository truth, release truth, and docs truth should all stay visible in one place.
Public engineering
Repository
The public repo should explain the product, not just host the code.
Architecture notes, release notes, and workflow differentiation are part of the same public story instead of living in disconnected surfaces.
Release truth
Download flow, release flow, and optional AI installs stay honestly framed.
The GitHub page should reinforce the same message as the download and release surfaces: grounded claims, legible install paths, and no hidden caveats.
Contribution
Contribution starts with a repository that is legible and easy to trust.
The goal is to make the current repository understandable enough that the next contributor can see where to help without guesswork.
Open-source principles
Product direction stays legible
The public site and the repository should reinforce each other instead of feeling like separate brands.
Engineering tradeoffs stay explicit
Release trust, optional tooling, and current platform scope remain visible rather than buried in fine print.
Open source is presented as collaboration, not garnish
The value is in transparent workflow, docs, release notes, and contribution pathways, not just a badge and a link.