druid.io - Community

Druid | Druid Community

Druid.io Spined HTML

Druid | DruidPolityTechnology Use Cases Powered By DocsPolityDownload MENU MENU DruidPolityCommunity Most discussion well-nigh Druid happens over email and GitHub. The Druid polity is in the process of migrating toTriggermanby way of theTriggermanIncubator. As we proceed withal 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. User mailing list druid-user@googlegroups.com for unstipulated discussionMinutiaemailing list dev@druid.apache.org for discussion well-nigh project minutiae GitHub druid-io/druid issues and pull requests (watch to subscribe) Meetups Druid meetups for variegated meetup groups virtually the world. IRC #druid-dev on irc.freenode.net Contributing Druid is a community-led project and we are delighted to receive contributions of anything from minor fixes to big new features. What to work on If you have an itch to scratch, then by all ways do that! Fixing bugs you run into, or subtracting 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.Lawmakingreview of pull requests (even if you are not a committer), full-length suggestions, reporting bugs, documentation and usability feedback all matter immensely.Flipsidebig way to help is through vendee 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. Getting your changes wonted Patches to Druid are washed-up through GitHub pull requests. Pull requests require one clearance (+1) from an established committer on lawmaking and text (for documentation) levels. The exception is major architectural changes or API changes, and/or changes to HTTP requests and responses (e. g. a new HTTP endpoint) Interfaces for extensions Server configuration (e. g. interchange the policies of a config property) Emitted metrics Other major changes, judged by the discretion of Druid committers warrant spare diamond and compatibility review. Such pull requests require diamond approvals from three variegated committers (one of them could moreover be the tragedian of the pull request). For those, it can help to discuss things on the druid-development list or a github issue beforehand. In unstipulated please follow the contributing guidelines when sending in pull requests. This will help review proceed as quickly as possible. For lawmaking contributions, we require that you stipulate to a Contributor License Agreement (CLA) surpassing we can winnow your code. You can find our CLA on and sign it directly on our CLA page Committers Committers are collectively responsible for Druid's technical management. This involves setting the direction of the project, contributing code, and reviewing lawmaking unsalaried by others. You don't need to be a committer to contribute- pull requests are welcome from anyone. Name Organization Charles Allen Snap David Lim Imply Eric Tschetter Splunk Fangjin Yang Imply Gian Merlino Imply Himanshu Gupta Splunk Jihoon Son Imply Jonathan Wei Imply Julian Hyde Looker Jun Rao Confluent Kurt Young Alibaba Lijin Bin Alibaba Maxime Beauchemin Lyft Mohamed Slim Bouguerra Hortonworks Navis Ryu SK Telecom Nishant Bangarwa Hortonworks Parag Jain Lyft P. Taylor Goetz EPAM Roman Leventov Snap Xavier Léauté Confluent Becoming a committer If you'd like to wilt 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.Unstipulatedcommitter guidelines 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: You can merge your own pull request if it fits the rest of the criteria. A worldwide thing to see is "+1 without travis" from other committers. A pull request should have at least one +1 from a committer who is not the author, on the "code/textual" level of review. Pull requests which have just one +1 from a committer couldn't be merged older than without 3 working days since PR submission. A pull request with just one +1 could be merged only by (or in coordination with) the committer who provided the review. Because the reviewer may think that the PR is ramified or risky unbearable that needs flipside pair of vision to squint at it. If this is the case, the first reviewer should indicate this in the PR clearance message. If a pull request has two or increasingly +1's from committers who are not the author, it could be merged immediately and by any committer. But still, unbearable time since the PR submission should pass to requite folks a reasonable endangerment to indicate a desire to scuttlebutt on the pull request. AKA: don't merge a pull request that was submitted Friday evening until at least 1~2 regular work days have passed. Use good judgement here. Major architectural and backwards incompatible changes, or changes which have long-term maintainance consequences (see examples in the "Getting your changes accepted" section above), should have at least three +1's from committers, on the "design" level of review. One clearance could be from the tragedian of the PR. The first committer who indicates that a PR needs diamond review should add theDiamondReview tag to such a pull request. Travis-CI should pass or have some very good reason why it won't pass for a pull request. You reasonably believe that all comments have been addressed. You are expected to be the champion for your own pull requests. Being a champion on a pull request can be a significant undertaking depending on the size of the lawmaking transpiration and what parts of the lawmaking it touches. It may require communicating with other developers, reconciling differences, organizing polity feedback, and/or pursuit up with people who have commented in a pull request to ensure comments have been addressed. Sometimes lawmaking is presented as a work-in-progress or as a point of discussion. Use the WIP or Discuss tags on a pull request in such a case. If a pull request you are championing is taking longer than expected to merge, be sure to raise the issue in the developer sync. Limit the number of pull requests you are championing at the same time. Prioritize lawmaking reviews to squint at pull requests that are blockers for the next release (see the Milestone marker on the pull request) Help serve as champion for pull requests that originate from new committers. If you finger a pull request is required for the next release, mark it as such in the Milestone of the pull request. Do not scuttlebutt on a pull request unless you are willing to follow up on the edits.Requitepriority to getting older pull requests merged. (Either as their champion or as an zippy commenter) And most importantly.. the PMC desires to ensure a positive and constructive developer experience! If you find that things are not functioning to your expectations, pleaes raise the issue. Remember, we all want to see this project thrive! Governance The PMC (Project Management Committee) is responsible for the legalistic aspects of the Druid project. The responsibilities of the PMC include: Approving releases Nominating new committers Maintaining the project's shared resources, including the github account, mailing lists, websites, social media channels, etc. Maintaining guidelines for the project Community ·  Download ·  Powered by Druid ·  FAQ ·  License  ·   ·  Except where otherwise noted, licensed under CC BY-SA 4.0