Skip to main content

How to Contribute

Apache Fluss is an open, community-driven project, and every improvement — from fixing a typo to designing a major new feature — comes from contributors like you. Contributions shape the project's direction, harden its quality, and help other users succeed. Whether you are filing your first bug report or landing a large feature, there is a place for you in the community.

This section collects the guides you need to make that journey smooth. Start with the contribution path that fits what you want to do, then follow the detailed guide for the specifics.

Choose Your Contribution Path​

Report a Bug or Request a Feature​

If you have found a defect, have a question the docs could not answer, or have an idea for a new capability, the best first step is to open an issue. This gives the community visibility into the problem and a place to discuss the solution before any code is written.

Good for: users of any experience level who want to help improve Fluss without writing code.

Contribute Code​

Code contributions — bug fixes, new features, performance improvements, refactors — are the heart of the project. Fluss follows a discuss first, implement after workflow so that reviewers and contributors stay aligned on the approach before effort is spent on a pull request.

  • Follow the Contribute Code guide for the end-to-end process: discuss, implement, review, and merge.
  • New to the codebase? Look at the good first issues to find a well-scoped task.

Good for: developers who want to dive into the Fluss codebase, from small fixes to large features.

Contribute Documentation​

Clear documentation makes Fluss usable. Fixing a broken link, clarifying a concept, or adding a full guide for a new feature are all valuable contributions, and they are often the fastest way to start contributing.

  • Follow the Contribute Documentation guide for how the docs site is structured, how to preview changes locally, and how versioned docs work across release branches.

Good for: contributors who want to improve the user experience, including those who prefer writing over coding.

Contribute Blog Posts​

Blog posts are how the community shares use cases, deep dives, tutorials, and release announcements. Blog content lives in a separate repository, apache/fluss-blog, and is published independently from the main documentation.

Good for: practitioners who want to share experience, demos, or technical deep dives with the wider community.

Review Pull Requests​

Reviewing is one of the most valuable contributions you can make. Good reviews keep the code base healthy, share knowledge across the community, and give contributors a great experience.

Good for: experienced contributors and committers who want to help others land their changes.

Getting Started Based on Your Experience​

New to Fluss? Start small. File a bug report when you hit one, fix a typo you notice in the docs, or pick up a good first issue labeled for newcomers.

Comfortable with the project? Look through the open issues for unassigned work that matches your interests, or propose an improvement you have wanted to see.

Experienced contributor? Help review pull requests, mentor newcomers on issues, or drive a larger feature through a Fluss Improvement Proposal (FIP).

Connect with the Community​

Contributions are easier when you are connected with other contributors. Join the conversation on:

  • GitHub Discussions — design questions, usage help, and general discussion.
  • Slack — real-time chat with contributors and users.
  • Mailing Lists — dev@fluss.apache.org for development, user@fluss.apache.org for user questions.

Thank you for helping make Apache Fluss better.