👍🎉 First off, thanks for taking the time to contribute! 🎉👍
Welcome to the discovery repository! The following is a set of guidelines for contributing to this repo and its packages. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
Note: Please don't file an issue to ask a question. You'll get faster results by using the resources below.
This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
Before creating bug reports, please check the before-submitting-a-bug-report checklist as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible. Fill in the issue_template.md, the information it asks for helps us resolve issues faster.
Note: If you find a Closed issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
- Confirm the problem is reproducible in the latest version of the software
- Check the Debugging Wiki. You might be able to find the cause of the problem and fix things yourself.
- Perform a cursory search of project issues to see if the problem has already been reported. If it has and the issue is still open, add a comment to the existing issue instead of opening a new one.
Bugs are tracked as GitHub issues. Issues should provide the following information by filling in the issue_template.md.
Explain the problem and include additional details to help maintainers reproduce the problem:
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as many details as possible.
- Provide specific examples to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use Markdown code blocks.
- Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
- Explain which behavior you expected to see instead and why.
- Include screenshots which show you following the described steps and clearly demonstrate the problem.
Provide more context by answering these questions:
- Did the problem start happening recently (e.g. after updating to a new version of the software) or was this always a problem?
- If the problem started happening recently, can you reproduce the problem in an older version of the software? What's the most recent version in which the problem doesn't happen?
- Can you reliably reproduce the issue? If not, provide details about how often the problem happens and under which conditions it normally happens.
Include details about your configuration and environment:
- Which version of the software are you using?
- What OS & Version are you running?
- For Linux - What kernel are you running? You can get the exact version by running
uname -ain your terminal.
- For Linux - What kernel are you running? You can get the exact version by running
- Are you running in a virtual machine? If so, which VM software are you using and which operating systems and versions are used for the host and the guest?
- Are you running in a docker container? If so, what version of docker?
- Are you running in a a Cloud? If so, which one, and what type/size of VM is it?
- What version of Java are you running?
This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.
Before creating enhancement suggestions, please check the before-submitting-an-enhancement-suggestion list as you might find out that you don't need to create one. When you are creating an enhancement suggestion, please include as many details as possible. Fill in the issue_template.md, including the steps that you imagine you would take if the feature you're requesting existed.
- Check the Debugging Wiki. You might be able to find the cause of the problem and fix things yourself.
- Perform a cursory search of project issues to see if the problem has already been reported. If it has and the issue is still open, add a comment to the existing issue instead of opening a new one.
Enhancement suggestions are tracked as GitHub issues. Issues should and provide the following information by filling in the issue_template.md and providing the following information:
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks.
- Describe the current behavior and explain which behavior you expected to see instead and why.
- Include screenshots which help you demonstrate the steps.
- Explain why this enhancement would be useful to most users.
- Does this enhancement exist in other clients?
- Specify which version of the software you're using.
- Specify the name and version of the OS you're using.
Start by looking through the 'good first issue' and 'help wanted' issues:
- Good First Issue - issues which should only require a few lines of code, and a test or two.
- Help wanted issues - issues which are a bit more involved than
good first issueissues.
The codebase is maintained using the "contributor workflow" where everyone without exception contributes patch proposals using "pull-requests". This facilitates social contribution, easy testing and peer review.
To contribute a patch, the workflow is as follows:
- Fork repository
- Create topic branch
- Commit patch
- Create pull-request, adhering to the coding conventions herein set forth
In general a commit serves a single purpose and diffs should be easily comprehensible. For this reason do not mix any formatting fixes or code moves with actual code changes.
Questions on architectural best practices will be guided by the principles set forth in Effective Java by Joshua Bloch
All code submissions must be accompanied by appropriate automated tests. The goal is to provide confidence in the code’s robustness, while avoiding redundant tests.
The process described here has several goals:
- Maintain Product quality
- Fix problems that are important to users
- Engage the community in working toward the best possible product
- Enable a sustainable system for maintainers to review contributions
- Further explanation on PR & commit messages can be found in this post: How to Write a Git Commit Message.
Please follow these steps to have your contribution considered by the approvers:
- Complete the CLA, as described in CLA.md
- Follow all instructions in PULL-REQUEST-TEMPLATE.md
- Include appropriate test coverage. Testing is 100% automated. There is no such thing as a manual test.
- Follow the Style Guides
- After you submit your pull request, verify that all status checks are passing
What if the status checks are failing?
If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.
While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted. Please refer to Code Reviews.
We use Google's Java coding conventions for the project. To reformat code, run:
./gradlew spotlessApply
Code style will be checked automatically during a build.
We have a set of coding conventions to which we try to adhere. These are not strictly enforced during the build, but should be adhered to and called out in code reviews.
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Provide a summary on the first line with more details on additional lines as needed
- Reference issues and pull requests liberally
| Label name | Search Link 🔎 | Description |
|---|---|---|
enhancement |
search | Feature requests. |
bug |
search | Confirmed bugs or reports that are very likely to be bugs. |
help wanted |
search | The core team would appreciate help from the community in resolving these issues. |
good first issue |
search | Less complex issues which would be good first issues to work on for users who want to contribute. |
info needed |
search | More information needs to be collected about these problems or feature requests (e.g. steps to reproduce). |
needs reproduction |
search | Likely bugs, but haven't been reliably reproduced. |
blocked |
search | Issues blocked on other issues. |
duplicate |
search | Issues which are duplicates of other issues, i.e. they have been reported before. |
wontfix |
search | The core team has decided not to fix these issues for now, either because they're working as intended or for some other reason. |
invalid |
search | Issues which aren't valid (e.g. user errors). |
do we want this? |
search | Seeking stakeholder consensus on proposed feature. |