Most discussion about Druid happens over email and GitHub, but those aren't the only way to interact with the Druid community. We also do chat, meetups, and more. Check out the following resources if you're looking for help, to discuss Druid development, or just stay up to date:
#druidon the Apache Slack team. Please use our invitation link to join, and once you join, add the
Third party companies also provide commercial support and services for Druid, including:
Druid is a community-led project and we are delighted to receive contributions of anything from minor fixes to big new features.
If you have an itch to scratch, then by all means do that! Fixing bugs you run into, or adding features you need, are both immensely helpful.
If you're looking for some starter projects, we maintain a list of issues suitable for new developers.
There are plenty of ways to help outside writing Druid code. Code review of pull requests (even if you are not a committer), feature suggestions, reporting bugs, documentation and usability feedback all matter immensely. Another big way to help is through client libraries, which are avaialble in a variety of languages. If you develop a new one, we'll be happy to include it in the list.
Patches to Druid are done through GitHub pull requests.
Pull requests require one approval (+1) from an established committer on code and text (for documentation) levels. The exception is major architectural changes or API changes, and/or changes to
warrant additional design and compatibility review. Such pull requests require design approvals from three different committers (one of them could also be the author of the pull request). For those, it can help to discuss things on the Druid development list firstname.lastname@example.org or a github issue beforehand.
In general please follow the contributing guidelines when sending in pull requests. This will help review proceed as quickly as possible.
All Pull Requests are automatically tested on Travis CI on both AMD64 and ARM64 architectures.
Committers are collectively responsible for Druid's technical management. This involves setting the direction of the project, contributing code, and reviewing code contributed by others.
You don't need to be a committer to contribute- pull requests are welcome from anyone.
|Chi Cao Minh||Imply|
|Egor Rashin||Rill Data|
|Mohamed Slim Bouguerra|
|Navis Ryu||SK Telecom|
|Parag Jain||Rill Data|
|P. Taylor Goetz||EPAM|
|Xinyu Zhang||Qihoo 360|
If you'd like to become a committer, that's great! Please contact one of the existing committers for a walk through the process. Basically, what we're looking for is an interest in ongoing contributions to Druid.
If you are an official Druid committer then congratulations! You are part of a fantastic group of people. Here are some guidelines to follow to help ensure the Druid project continues to grow and improve:
Design Reviewtag to such a pull request.
Discusstags on a pull request in such a case.
Remember, we all want to see this project thrive!
The PMC (Project Management Committee) is responsible for the administrative aspects of the Druid project. The responsibilities of the PMC include: