Governance
Licensing
Every project is MIT licensed and stays MIT licensed. Releases already published cannot be relicensed retroactively, and we have no intention of relicensing future ones.
This is structural, not just a promise. The styling engine (OpenUXKit) was forked from the last MIT-licensed upstream source precisely so the projects do not depend at runtime on a package scope controlled by anyone else. A licensing change upstream cannot reach these packages.
Maintainers
Commit access is granted on sustained, review-quality contribution rather than employer or affiliation. No single company controls the roadmap, and none funds it.
We are actively building out the maintainer team. If you know these libraries well, that is exactly the background we want. See contributing.
How changes get made
- All changes land through pull requests with review. No direct pushes to main.
- Breaking changes to a stable API need a documented migration path before they are accepted.
- Bug fixes and dependency updates take priority over new features while the project is stabilizing.
- Discussion happens in public on GitHub issues, so the reasoning behind a decision is still readable later.
Releases
Packages are published to npm under the @openvue and
@openuxkit scopes, with
semantic versioning and dist-tags (alpha, beta,
rc, latest) marking maturity. Every release gets a changelog entry.
Security
Report vulnerabilities privately through the security policy, not as a public issue. We will coordinate disclosure with the reporter.
Continuity
The projects live under a GitHub organization with multiple owners rather than a personal account, and everything needed to build and publish them is in the repositories. If the current maintainers step away, anyone can fork the work under MIT, which is the same guarantee that made this foundation possible in the first place.
Code of conduct
Participation across all repositories and in the Discord server is covered by the code of conduct.