Skip to content
Governance & community

Governance & community

Runink River is an open-source project with written, open governance. Today it is a single-vendor project stewarded by Runink, with one maintainer, and a written path to vendor-neutral governance under a foundation. Incubation at a foundation is planned; nothing has been submitted. The documents below are the authoritative text; this page summarises them.

The documents

DocumentWhat it covers
GOVERNANCE.mdroles, how decisions are made, how to become a maintainer, neutrality, the path to a foundation
CHARTER.mdthe draft technical charter for the foundation era (not in force)
MAINTAINERS.mdwho the maintainers are, their affiliation and signing key
CONTRIBUTING.mdhow to send a change, the DCO, the test policy
CODE_OF_CONDUCT.mdContributor Covenant 2.1
SECURITY.mdprivate reporting, response targets, coordinated disclosure
ROADMAP.mdoutcomes and milestones (summary)
RELEASE.mdhow a release is cut, checked and signed (summary)
TRADEMARKS.mdthe project name and marks, and the project’s neutrality
ADOPTERS.mdwho uses Runink River (none listed yet) and how to add yourself
SUPPORT.mdwhere to get help
Foundation readinessthe foundation, OpenSSF and Apache Way criteria, with the evidence and the gaps
OpenSSF self-assessmentthe OpenSSF Best Practices criteria, one by one (not registered yet; no badge awarded)

Working in the open

If a decision is not recorded in the repository, it has not been made. Proposals, reviews, votes and their results happen on GitHub issues, pull requests and Discussions, where anyone can read and take part. Only security reports and Code of Conduct reports are handled in private, and both end in a public record.

Roles

  • Users run Runink River. Contributors send issues, reviews, documentation, tests on real hardware or code.
  • Maintainers (MAINTAINERS.md; committers, in Apache terms) review and merge, triage issues and security reports, cut and sign releases, and enforce the invariants and the Code of Conduct.
  • The Technical Steering Committee (TSC): while there are fewer than five maintainers, all of them. From five, an elected TSC of three to seven with a chair, and no employer holding more than a third of the seats.

How decisions are made

Lazy consensus: a proposal is accepted if no maintainer objects within its review window. When consensus fails, any maintainer may call a TSC vote (+1, 0, -1) on the issue or pull request, so there is a public record.

ChangeNeeds
Bug fix, docs, a routine pin bump1 maintainer approval (not the author)
New feature, new package, new workflow1 approval and no objection within 3 working days
An invariant (s6, one kernel, encrypted ZFS root, secrets like /etc/shadow, the default-deny firewall, the sandbox deny-list, pinned upstreams, …)TSC vote, 2/3 majority, 7 days
Licensing, trademark, charter, governance, maintainersTSC vote, 2/3 majority, 7 days

While there is one maintainer, the “not the author” approval cannot be met: the maintainer merges their own pull requests once the required checks pass and the review window has run. That gap closes with the second maintainer.

Becoming a maintainer

About three months of sustained contribution of any kind (code, reviews, documentation, testing, packaging, helping users), a nomination by a maintainer, and a TSC vote. Your employer does not matter. The project needs a second maintainer, so this path is open now: start with Contributing.

Neutrality

Runink River ships no proprietary components and names no vendor’s product. Any vendor, Runink included, builds on it outside the repository, through the same public interfaces (external profiles, payloads, the first-boot contract). No vendor holds a veto outside the TSC, and maintainers disclose a conflict of interest before they vote. The project’s marks are held by Runink today, with the stated intent to transfer them to a foundation (TRADEMARKS.md).

Where to talk

ChannelUse it for
GitHub Discussionsquestions, ideas and proposals, announcements
GitHub Issuesbugs and agreed feature work
Pull requestschanges, reviews and every governance decision
Private vulnerability reporting or security@runink.orgsecurity problems only (how to report)

There is no mailing list, chat channel or community meeting yet. When one is created it is announced in Discussions and added to README.md.

Path to a foundation

PhaseState
0: private preparationdone
1: public, single-vendornow: the repository is public, governance is written down, one maintainer
2: foundation applicationplanned: the LF AI & Data Sandbox proposal is a draft and has not been submitted (docs/governance/LF-AIDATA.md)
3: vendor-neutralmarks and domain assigned to the foundation, charter adopted, maintainers from two or more organisations