Skip to content

Latest commit

 

History

History
51 lines (39 loc) · 2.27 KB

contributing.md

File metadata and controls

51 lines (39 loc) · 2.27 KB

How to Contribute

Contributions are greatly appreciated. The maintainers of Config Sync monitor issues and PRs and strive to provide timely feedback and reviews. For any questions or suggestions, reach to to the Config Sync maintainers on issues or discussions.

For small bug fixes and doc updates, just create a PR with your change. ConfigSync follows the Kubernetes contribution process, so fork the project, create a change and then submit a PR against the main branch which is the HEAD of development.

For larger changes and for anything that has a change to the CLI and API please write a design document first. This is to make sure the change is aligned with the direction of the project and doesn't conflict with other planned features. If you want input from the maintainers or the community before the design is completed, just create a WIP PR.

For faster reviews on PRs, make sure that the PR doesn't contain any conflicts and that all the checks are passing.

Contributor License Agreement

Contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution; this simply gives us permission to use and redistribute your contributions as part of the project. Head over to https://cla.developers.google.com/ to see your current agreements on file or to sign a new one.

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.

Code Reviews

All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult GitHub Help for more information on using pull requests.

Community Guidelines

This project follows Google's Open Source Community Guidelines.