Licensing, versioning & project policy
The questions that arrive from a legal or procurement inbox.
- What is open source and what is notThe open-core split, stated plainly — and which component falls on which side.
- Can I use TOVIO commercially?The short answer, what redistribution obliges, and where the line is.
- Using the TOVIO name and logoWhat the trademark policy permits, what it does not, and how to ask.
- What the version number meansPre-1.0, what is genuinely settled, and what may still change under you.
- Compatibility and deprecation promisesWhat is committed, per surface, and how a breaking change is announced.
- Format and protocol stabilityWhat is actually frozen, what is not, and what protects data you have already written.
- Contributing to TOVIOWhere to start, what is required before a first pull request, and what review will hold you to.
- How long a release is supportedThe support lifecycle, and what is committed so far.
- Service status and incidentsWhere to look when something hosted is not working.
- Third-party code and attribution noticesWhat TOVIO incorporates from others, and where the notices live.
- Who decides what, and howThe governance model today, the announced path away from it, and what is not the leader's to override.
- How architecture decisions are recordedWhat a decision record is, and how to use the archive when you are evaluating the project.
- What happens if the project stopsThe continuity question, answered with the mechanisms rather than reassurance.