Governance
Who maintains the openlakestream repositories, how pull requests and Lakestream Improvement Proposals (LIPs) are decided, and what isn't defined yet.
Lakestream is stewarded by StreamNative. The standard, Ursa, Ursa for Apache Kafka (UFK) and the related projects are developed in the openlakestream GitHub organization.
Maintainers
Each repository's maintainers are the code owners in its CODEOWNERS file. A code owner for the files a pull request touches reviews and approves it.
| Repository | Code owners |
|---|---|
| openlakestream/ursa | CODEOWNERS |
| openlakestream/kafka | CODEOWNERS |
| openlakestream/lips | CODEOWNERS |
| openlakestream/streaming-proof | CODEOWNERS |
openlakestream/leaderless-log-protocol doesn't have a CODEOWNERS file yet.
How decisions are made
- Pull requests. A code owner for the files a pull request touches reviews and approves it. Pull requests are squash-merged.
- LIPs. A LIP is accepted when its pull request in openlakestream/lips merges, after review by that repository's code owners and a maintainer of each component it changes. A LIP that isn't accepted is closed, with the reasons recorded on the pull request. See Improvement proposals.
- In public. Proposals, reviews and decisions happen in GitHub issues, Discussions and pull requests. The projects don't run a Slack workspace or a mailing list.
Not defined yet
There is no formal process yet for adding maintainers or settling disagreements between them.
Licensing
Lakestream, Ursa and UFK are licensed under the Apache License 2.0. Contributions are accepted under the Developer Certificate of Origin, with no CLA; see Contributing.
Improvement proposals (LIPs)
Lakestream Improvement Proposals (LIPs): when a change needs one, how a LIP is written, reviewed and accepted, and the index of LIPs.
Code of conduct
Every openlakestream repository follows the same code of conduct; this page states where it applies and how to report a problem.