23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
---
|
|
title: Community
|
|
keywords: usecases
|
|
sidebar: mydoc_sidebar
|
|
toc: false
|
|
permalink: community.html
|
|
---
|
|
|
|
## Contributing
|
|
We :heart: contributions. If you find a bug in the library or would like to add new features, go ahead and open
|
|
issues or pull requests against this repo. Before you do so, please sign the
|
|
[Uber CLA](https://docs.google.com/a/uber.com/forms/d/1pAwS_-dA1KhPlfxzYLBqK6rsSWwRwH95OCCZrcsY5rk/viewform).
|
|
Also, be sure to write unit tests for your bug fix or feature to show that it works as expected.
|
|
If the reviewer feels this contributions needs to be in the release notes, please add it to CHANGELOG.md as well.
|
|
|
|
If you want to participate in day-day conversations, please join our [slack group](https://join.slack.com/t/apache-hudi/signup).
|
|
If you are from select pre-listed email domains, you can self signup. Others, please add your email onto this [issue](https://github.com/uber/hoodie/issues/143)
|
|
|
|
## Becoming a Committer
|
|
|
|
Hoodie has adopted a lot of guidelines set forth in [Google Chromium project](https://www.chromium.org/getting-involved/become-a-committer), to determine committership proposals. However, given this is a much younger project, we would have the contribution bar to be 10-15 non-trivial patches instead.
|
|
Additionally, we expect active engagement with the community over a few months, in terms of conference/meetup talks, helping out with issues/questions on slack/github.
|