Skip to main content


Share your knowledge, experience, and ideas about Camunda with fellow users.

From something as little as a typo in the documentation to something as big as the proposal and contribution of a whole new module, we try to create a constructive athmosphere in which your contribution advances the Camunda community.


Help other users get their processes running by contributing knowledge on the Camunda forum

Error reports

Help make Camunda more robust by contributing error reports


Help make Camunda more awesome by contributing feature ideas


Make your idea part of Camunda by contributing code

Contributing Knowledge

Assist other users with implementing their processes with Camunda BPM on the user forum. By sharing your own solutions, you can initiate a constructive discussion around them, gain new insights, and help others.

Contributing Error Reports

Be it an error in our documentation or a bug in the core process engine, we welcome error reports of any kind so that we can improve Camunda steadily. Share your findings on the Camunda user forum. Help others track down the problem by providing a precise problem description and steps to reproduce the problem.

For anything code-related, consider creating a test case that reproduces the problem. See the unit testing template for a ready-made Java project that saves you the effort of setting up a Camunda Maven project from scratch.

Contributing Ideas

We strive to make Camunda BPM better every day. Check our roadmap for the features that we consider most useful to our community and that we are aiming to implement in the short term. Check our JIRA issue tracker for the entire backlog of feature ideas.

Do you miss a feature and have an idea how to make Camunda even more awesome? Don't hesitate to share your thoughts on the Camunda user forum. This allows Camunda users and developers to share their thoughts, to challenge and validate your proposal. If a consensus is reached, we can distill concise feature requests into the Camunda issue trackers (e.g. Camunda JIRA issue tracker for the core of Camunda BPM).

Contributing Code

Code contributions are your tool to get things done. In the core Camunda team, we continuously evaluate the backlog and prioritize tasks. We try to focus on those tasks that are most useful to a majority of users, yet we take the liberty to choose our own work. By providing code, you improve Camunda BPM and become independent of the core Camunda team's priorities.

The range of possible contributions covers:

Code contributions take error reports and feature ideas one step further. Unless it is a simple fix, we encourage you to share those on the user forum before providing the corresponding code. With this additional feedback cycle, you can get hints from experienced Camunda users and developers before investing a lot of effort into implementation.

Code can be contributed in two forms:

Core Codebase

Community Extension

Contributions must fit into the scope of Camunda BPM. The ultimate decision is up the Camunda core team. Suitable for anything, especially things that are not in the core scope of Camunda.
Code and API must have at least the quality of the core codebase. No restrictions on code quality and API design.
Once contributed, code is maintained and supported by Camunda. Code is maintained and supported by community members. Camunda offers github repository and testing infrastructure.
Features and fixes remain stable for any future Camunda 7 release. Project evolution is up to the maintainers.
Code is released as part of Camunda BPM release cycles. Release cycle is up to the maintainers.
Camunda announces major contributions on its communication channels (Blog, Twitter, ...). Possibility to provide content for distribution on Camunda communication channels.

See the list of existing community extensions to get an idea of what a community extension can be.

Throughout the contribution process, Camunda core developers and the community support you on the contributions forum with:

For larger contributions (core codebase or community extension), a Camunda core developer will be primarily responsible to guide you through the contribution process and remove obstacles wherever necessary. However, it is still you who has to drive the contribution.

See the Camunda github organization for all the repositories you may contribute to. Out of these, the primary ones are:

When writing code, make sure to adhere to the contribution guidelines that are provided in the respective repository. When you are done, submit your contribution as a pull request. A maintainer of the repository will review it and may request improvements. If everything is fine, your code will be merged.

Contributing Documentation

For documentation improvements, note that every page has a github link that directly takes you to the source file of the documentation page you are browsing.