Community

FlowDSL is open source (Apache 2.0) and community-driven. The specification, Studio editor, SDKs, and reference runtime are all developed in the open at github.com/flowdsl.

Ways to participate

Report a bug or request a feature

Open an issue on the relevant repository:

Ask a question

• GitHub Discussions — github.com/flowdsl/spec/discussions — the primary place for open-ended questions and design discussions
• Discord — discord.gg/flowdsl — real-time chat with maintainers and community members

Propose a spec change

Major spec changes go through an RFC (Request for Comments) process:

1. Open a GitHub Discussion in flowdsl/spec with the RFC label
2. Describe the problem, the proposed change, and any alternatives considered
3. The community and maintainers discuss for at least 2 weeks
4. If accepted, an issue is opened and a PR is authored against the spec

Minor additions (new optional fields, clarifications) can be proposed directly as a Pull Request.

Contribute code

See the Contributing Guide for how to set up your development environment and open a pull request.

Share your flows

Publish your FlowDSL examples in the flowdsl/examples repository. Real-world examples help the community understand what is possible and how to model different domains.

Governance

FlowDSL is currently maintained by a small core team. The roadmap is public at github.com/flowdsl/spec/projects. Major decisions are made through the RFC process.

Code of conduct

All community spaces (GitHub, Discord, discussions) follow the FlowDSL Code of Conduct. The short version: be respectful, be constructive, be welcoming.

Stay updated

• GitHub releases — watch flowdsl/spec for spec releases
• Changelog — github.com/flowdsl/spec/blob/main/CHANGELOG.md
• Blog — flowdsl.com/blog — announcements and deep-dives

Next steps

• Contributing Guide — how to contribute code and docs
• Code of Conduct — community standards
• Migration — upgrade guides between spec versions