Get help using Kudu or contribute to the project on our mailing lists or our chat room:
Developer mailing lists
Other developer resources
There are lots of ways to get involved with the Kudu project. Some of them are listed below. You don’t have to be a developer; there are lots of valuable and important ways to get involved that suit any skill set and level.
If you want to do something not listed here, or you see a gap that needs to be filled, let us know.
Community is the core of any open source project, and Kudu is no exception. Participate in the mailing lists, requests for comment, chat sessions, and bug reports.
Let us know what you think of Kudu and how you are using it. Send links to blogs or presentations you’ve given to the kudu user mailing list so that we can feature them.
If you see problems in Kudu or if a missing feature would make Kudu more useful to you, let us know by filing a bug or request for enhancement on the Kudu JIRA issue tracker. The more information you can provide about how to reproduce an issue or how you’d like a new feature to work, the better.
You can submit patches to the core Kudu project or extend your existing codebase and APIs to work with Kudu. The Kudu project uses Gerrit for code reviews. Please read the details of how to submit patches and what the project coding guidelines are before your submit your patch, so that your contribution will be easy for others to review and integrate.
In order for patches to be integrated into Kudu as quickly as possible, they must be reviewed and tested. The more eyes, the better. Even if you are not a committer your review input is extremely valuable. Keep an eye on the Kudu gerrit instance for patches that need review or testing.
Making good documentation is critical to making great, usable software. If you see gaps in the documentation, please submit suggestions or corrections to the mailing list or submit documentation patches through Gerrit. You can also correct or improve error messages, log messages, or API docs.
If you’d like to translate the Kudu documentation into a different language or you’d like to help in some other way, please let us know. It’s best to review the documentation guidelines before you get started.
The examples directory includes working code examples. As more examples are requested and added, they will need review and clean-up. This is another way you can get involved.
If you’re interested in hosting or presenting a Kudu-related talk or meetup in your city, get in touch by sending email to the user mailing list at email@example.com so that we can feature them.
Presentations about Kudu are planned or have taken place at the following events:
The Kudu community does not yet have a dedicated blog, but if you are
interested in promoting a Kudu-related use case, we can help spread the word.
Send email to the user mailing list at firstname.lastname@example.org with your content and we’ll help drive traffic.