Everyone is encouraged to contribute to this project. We welcome of course code changes, but we are also grateful for bug reports, feature suggestions, helping with testing and documentation, or simply spreading the word about projectnessie.
Please use GitHub issues for bug reports and feature requests and GitHub Pull Requests for code contributions.
More information are available at https://projectnessie.org/develop/
You must agree to abide by the Project Nessie Code of Conduct.
Issues can be filed on GitHub. Please add as much detail as possible. Including the version and a reproducer. The more the community knows the more it can help :-)
If you have a feature request or questions about the direction of the project please as via a GitHub issue.
We are excited to accept new contributors and larger changes. Please post a proposal before submitting a large change. This helps avoid double work and allows the community to arrive at a consensus on the new feature or improvement.
The development process doesn't contain many surprises. As most projects on github anyone can contribute by forking the repo and posting a pull request. See GitHub's documentation for more information. Small changes don't require an issue. However, it is good practice to open up an issue for larger changes.
Changes must adhere to the style guide and this will be verified by the continuous integration build.
- Java code style is Google style.
- Kotlin code style is ktfmt w/ Google style.
Java + Kotlin code style is checked by Spotless with google-java-format during build.
Follow the instructions for Eclipse or IntelliJ, note the required manual actions for IntelliJ.
Java and Kotlin code style issues can be fixed from the command line using
./gradlew spotlessApply.
Anyone can take part in the review process and once the community is happy and the build actions are passing a Pull Request will be merged. Support must be unanimous for a change to be merged.
Please see our Security Policy