Most discussion about Druid happens over email and GitHub.
The Druid community is in the process of migrating to Apache by way of the Apache Incubator. As we proceed along this path, our site will move from http://druid.io/ to https://druid.apache.org/, and our mailing lists and Git repositories will be migrated as well.
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 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.
For code contributions, we require that you agree to a Contributor License Agreement (CLA) before we can accept your code. You can find our CLA on and sign it directly on our CLA page
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.
|Mohamed Slim Bouguerra||Hortonworks|
|Navis Ryu||SK Telecom|
|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: