Skip to main content

Community

Every volunteer project obtains its strength from the people involved in it. We invite you to participate as much or as little as you choose.

You can:

  • Use our project and provide a feedback.
  • Provide us with the use-cases.
  • Report bugs and submit patches.
  • Contribute code, documentation.

Mailing list

NameDescSubscribeUnsubscribePostArchive
user@curator.apache.orgUsage issues and questionsSubscribeUnsubscribePostArchive
dev@curator.apache.orgDevelopment related discussionsSubscribeUnsubscribePostArchive
commits@curator.apache.orgAll commits to our repositoriesSubscribeUnsubscribeRead only listArchive

Please make sure you are subscribed to the mailing list you are posting to!

If you are not subscribed to the mailing list, your message will either be rejected or you won't receive the response.

How to subscribe to a mailing list

Before you can post a message to a mailing list, you need to subscribe to the list first.

  1. Send an email without any contents or subject to listname-subscribe@curator.apache.org. (replace listname with dev or user)
  2. Wait till you receive an email with the subject "confirm subscribe to listname@curator.apache.org". Reply to that email, without editing the subject or including any contents.
  3. Wait till you receive an email with the subject "WELCOME to listname@curator.apache.org".

If you email us with a code snippet, make sure that:

  • you do not link to files in external services as such files can change, get deleted or the link might break and thus make an archived email thread useless
  • you paste text instead of screenshots of text
  • you keep formatting when pasting code in order to keep the code readable
  • there are enough import statements to avoid ambiguities

Issue tracker

We use JIRA to track all code related issues: https://issues.apache.org/jira/browse/CURATOR

You must have a JIRA account in order to log cases and issues.

Bug reports

Found bug? Enter an issue in the issue tracker.

Before submitting an issue, please:

  • Verify that the bug does in fact exist.
  • Search the issue tracker to verify there is no existing issue reporting the bug you've found.
  • Consider tracking down the bug yourself in the source code of Curator and submitting a patch along with your bug report. This is a great time saver for the Curator developers and helps ensure the bug will be fixed quickly.

Enhancement

Enhancements or new feature proposals are also welcome. The more concrete and rationale the proposal is, the greater the chance it will be incorporated into future releases.

Source code