Contributing to ObzenFlow
Code, docs, feedback, ideas. All contributions welcome.
Get started
The framework and its foundational crates are open source and accepting contributions. The main repo is the best place to start, or dive into a standalone library that powers ObzenFlow.
The main framework repo. Includes the DSL, runtime, journals, middleware, AI stages, and a structured examples directory with 20+ runnable demos organized as a five-tier learning path.
View repo →A tiny library for phantom-typed ULIDs. Type-safe identifiers for flows, stages, and events.
View repo →An async-first finite state machine library for Rust. Powers flow lifecycle and stage transitions.
View repo →WASM-friendly crate for representing and validating flow and pipeline graphs.
View repo →New to open source? These smaller crates are a friendly place to start. See the contributing guide for details.
Stay connected
Follow development and read about the ideas behind ObzenFlow.
Share feedback
We're actively refining the philosophy and documentation. If something resonates or feels off, open a discussion or reach out. Thoughtful feedback on the ideas is just as valuable as code contributions.
Ways to contribute
There are many ways to get involved.
Features, performance, and correctness
Guides, tutorials, and API docs
Real-world use cases, connectors, and ecosystem tooling
Edge cases, property testing, and fuzzing
We'll tag issues with good first issue and help wanted to help you find the right entry point.
License and sign-off
Core framework repositories in the ObzenFlow org are licensed under either MIT or Apache-2.0, at your option. Website branding, artwork, and media remain all rights reserved, while original written website content is licensed under CC BY-NC-SA 4.0. See site legal notices.
We use DCO (Developer Certificate of Origin), a lightweight way for contributors to certify they have the right to submit their work. Our decision to use DCO rather than a CLA is a commitment to open source licensing for framework code while still protecting project trademarks and original website assets.
When you contribute, sign off your commits with git commit -s. This adds a Signed-off-by line to your commit message attesting that you wrote the code or have the right to pass it on.
If your organization requires a CLA, your contributions may be incompatible with our free and open source software (FOSS) philosophy, and that's okay. Reach out to your internal open source stewards to help you understand the differences between DCO and CLA and your options.
We'd love your help
Open source thrives on contributions of all kinds: code, documentation, feedback, bug reports, and ideas. If you're unsure where to start, open an issue and say hello. We're happy to help you find something that fits.