The Code, our TODOs and Documentation is maintained on GitHub. All Issues should be opened in that repository.
Features, bugs and any issues regarding the documentation should be filed as
GitHub Issue in
our repository. We use labels like kind/feature, kind/bug, area/aws to
organize the issues. Issues labeled good first issue and help wanted are
especially good for a first contribution. If you want to pick up an issue just
leave a comment.
This project uses the well-known pull request process from GitHub. To submit a pull request, fork the repository and push any changes to a branch on the copy, from there a pull request can be made in the main repo. Merging a pull request requires the following steps to be completed before the pull request will be merged:
- ideally, there is an issue that documents the problem or feature in depth.
- code must have a reasonable amount of test coverage
- tests must pass
- PR needs be reviewed and approved
Once these steps are completed the PR will be merged by a code owner.
We're using the pull request assignee feature to track who is responsible
for the lifecycle of the PR: review, merging, ping on inactivity, close.
We close pull requests or issues if there is no response from the author for
a period of time. Feel free to reopen if you want to get back on it.
Note: Pull requests that are labelled with size/l and above MUST have at least TWO approvers for it to be merged. Please respect this policy to ensure the quality of code in this project.