A project to empower our open source community extension maintainers, and encourage new contributors to get started contributing to the Camunda open source ecosystem.
- What is the Camunda Community Hub?
- How to contribute
- Communication guidelines and expectations
- Troubleshooting and community support
- Inspiration
The Camunda Community Hub is a GitHub Organization for all of our community-contributed extensions.
Extensions in the Camunda Community Hub organization are independently led and maintained projects by members of the broader Camunda open source community, some of whom happen to be Camunda employees, or are projects/tutorials that are created and maintained by the Camunda Developer Relations team!
We’ve put together some commonly asked questions and answers about the Camunda Community Hub, our approach to open source contributions and maintainership, and how we hope to empower our open source community in the future.
- Start a new community extension by opening an issue using the
New Community Extension Proposaltemplate. Follow our complete documentation on creating a new extension here. - Transfer your existing repository into the Camunda Community Hub (do not fork it into the Hub) following these instructions.
- Browse our existing projects and contribute -- code and non-code contributions welcome!
All contributors also must sign our CLA and agree to our Code of Conduct. Then, review our Contributor Guide.
- Contributor guide
- Issue triage and labeling
- Maintainers, start here
- Maintainer & reviewer expectations
- Automated release documentation
- Using our groupId for Java builds
As is the nature of open source software, maintainers and extension creators often wear many hats. These range from administrative, to QA, and much more. As extensions in the Camunda Community Hub are community led, it is crucial that users of extensions understand that maintainers are often working on community extensions in their free time. Please remember to be kind, and follow the Camunda Community Code of Conduct and Camunda Community Values when interacting with project maintainers.
Keep in mind that communication styles vary, and no two individuals communicate in the same way. Please do your best to remain helpful, and try to avoid making sweeping demands or generalizations whenever possible. It is expected that Maintainers will follow the Camunda Code of Conduct when interacting with community members, and the same holds true for community members interacting with extension maintainers.
Not ideal: “This feature doesn’t work, please fix it!”
Preferred: “This feature doesn’t work as expected when I [do XYZ], do you have any suggestions as to how I can fix it? Thank you so much!”
When closing a pull request as a community extension maintainer, please keep in mind the following examples of helpful communication:
Not ideal “This is not following the current pull request conventions! I’m closing this issue.”
Preferred: “I am closing this PR because this extension can’t support [use case]. In its current form, it would be improved by/better contributed to [XYZ]. Thank you so much for your work on this!”
If you’re encountering a problem with an extension or the Community Hub, remember that the community is here to help! Please feel free to start a post on the Camunda community forums, or the Camunda Community Hub GitHub Discussions.
If you have a question related to getting started contributing to the Camunda open source ecosystem, or need to reach out to the Camunda team, you can start a topic in our Discussions, tag the Camunda DevRel team in an Issue or PR, or reach out via email: [email protected].
We highly encourage you to post on the Camunda community forums about your extension, its wider impact for the open source community, and what made you decide to build a community extension.
The Camunda Developer Relations team exists to serve the Camunda developer community, from internal employees to open source contributors, Enterprise customers, and the broader tech community. It is our goal to provide opportunities for developers to be more successful by making them aware of our solutions, enabling them to be successful through great experiences, and fostering a culture of collaboration.
This documentation was inspired by the following resources: