SlateDB would like to join Commonhaus #213
Closed
criccomini
started this conversation in
Joining Commonhaus
Replies: 4 comments 9 replies
-
This looks very interesting. |
Beta Was this translation helpful? Give feedback.
1 reply
-
@gavinking One thing I should have asked in the PR: I'm not totally clear on what next steps are after opening the discussion and bootstrapping PR. |
Beta Was this translation helpful? Give feedback.
3 replies
-
🎉 Welcome to Commonhaus! |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Project information
Do you have authority to represent this project?
Describe your project
SlateDB is an embedded storage engine built as a log-structured merge-tree written in Rust. Unlike traditional LSM-tree storage engines, SlateDB writes data to object storage (S3, GCS, ABS, MinIO, Tigris, and so on). Leveraging object storage allows SlateDB to provide bottomless storage capacity, high durability, and easy replication.
SlateDB is useful for stream processing state management, durable execution persistence, durable caches, workflow orchestration, data lakes, and more. It's a library that's intended to be a building block for infrastructure that wishes to store row-based data on the cloud.
The project has committers from Responsive, Microsoft, Jamsocket, Databend, and Materialized View. It's currently being deployed at Tensorlake and Responsive.
Motivation for joining Commonhaus
We have three main goals:
I have extensive experience with Apache (I'm on the PMC, created Apache Samza, and mentored Apache Airflow), but opted to avoid it for this project because it's a bit heavy weight. I was hoping CNCF might fit our needs. We applied to the sandbox. But after several months, I'm finding it very heavy on bureaucracy as well. It's a distraction, and getting in the way. @gunnarmorling turned me on to Commonhaus and it looks like a perfect fit for our needs.
Nope! Just excited to join. :)
Things that must be done (bootstrap phase)
Review the bylaws, especially sections about projects, decision making, and voting for significant decisions.
Read the bootstrapping agreement.
If all is well, and you agree to participate in the bootstrapping phase to help us build this thing, then create a PR with the following:
The commit should be "Signed-off-by" your GH login (
git commit -s -m "<project> bootstrapping agreement, yyyy-mm-dd"
)Beta Was this translation helpful? Give feedback.
All reactions