Thank you so much for wanting to contribute to Guava! Here are a few important things you should know about contributing:
We make changes to Guava‘s public APIs, including adding new APIs, very carefully. Because of this, if you’re interested in seeing a new feature in Guava, the best approach is to create an issue (or comment on an existing issue if there is one) requesting the feature and describing specific use cases for it.
If the feature has merit, it will go through a thorough process of API design and review. Any code should come after this.
Unless the change is a trivial fix such as for a typo, it‘s generally best to start by opening a new issue describing the bug or feature you’re intending to fix. Even if you think it‘s relatively minor, it’s helpful to know what people are working on. And as mentioned above, API changes should be discussed thoroughly before moving to code.
Some examples of types of pull requests that are immediately helpful:
Guidelines for any code contributions:
git rebase -i). Do your best to have a well-formed commit message for the change.
Due to Guava‘s nature as a subset of Google’s internal codebase which is automatically synced to the public GitHub repository, we are unable to merge pull requests directly into the master branch. Instead, once a pull request is ready for merging, we'll make the appropriate changes in the internal codebase and, when the change is synced out, give the pull request author credit for the commit.
Contributions to any Google project must be accompanied by a Contributor License Agreement. This is not a copyright assignment; it simply gives Google permission to use and redistribute your contributions as part of the project.
You generally only need to submit a CLA once, so if you‘ve already submitted one (even if it was for a different project), you probably don’t need to do it again.