external-secrets/docs/contributing-process.md

## Project Management
The Code, our TODOs and Documentation is maintained on
[GitHub](https://github.com/external-secrets/external-secrets). All Issues
should be opened in that repository.

## Issues

Features, bugs and any issues regarding the documentation should be filed as
[GitHub Issue](https://github.com/external-secrets/external-secrets/issues) 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.

## Submitting a Pull Request

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.

## Proposal Process
Before we introduce significant changes to the project we want to gather feedback
from the community to ensure that we progress in the right direction before we
develop and release big changes. Significant changes include for example:
* creating new custom resources
* proposing breaking changes
* changing the behavior of the controller significantly

Please create a document in the `design/` directory based on the template `000-template.md`
and fill in your proposal. Open a pull request in draft mode and request feedback. Once the proposal is accepted and the pull request is merged we can create work packages and proceed with the implementation.

## Cutting Releases

The external-secrets project is released on a as-needed basis. Feel free to open a issue to request a release. Details on how to cut a release can be found in the `RELEASE.md` file in the repo.
feat: add docs (#39) * feat: add docs Signed-off-by: Moritz Johner <beller.moritz@googlemail.com> 2021-03-01 07:31:02 +00:00			`## Project Management`
			`The Code, our TODOs and Documentation is maintained on`
			`[GitHub](https://github.com/external-secrets/external-secrets). All Issues`
			`should be opened in that repository.`

			`## Issues`

			`Features, bugs and any issues regarding the documentation should be filed as`
			`[GitHub Issue](https://github.com/external-secrets/external-secrets/issues) 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.`

			`## Submitting a Pull Request`

Update contributors doc to include forking repo Mention in the contributors guide that in order to create a PR, branches must be pushed to a forked copy of the repo. 2021-05-04 10:15:11 +00:00			`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:`
feat: add docs (#39) * feat: add docs Signed-off-by: Moritz Johner <beller.moritz@googlemail.com> 2021-03-01 07:31:02 +00:00
			`* 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.`
feat(docs): add proposal process, add bi-weekly meeting 2022-01-22 22:26:59 +00:00			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.`

			`## Proposal Process`
			`Before we introduce significant changes to the project we want to gather feedback`
			`from the community to ensure that we progress in the right direction before we`
			`develop and release big changes. Significant changes include for example:`
			`* creating new custom resources`
			`* proposing breaking changes`
			`* changing the behavior of the controller significantly`

			Please create a document in the `design/` directory based on the template `000-template.md`
			`and fill in your proposal. Open a pull request in draft mode and request feedback. Once the proposal is accepted and the pull request is merged we can create work packages and proceed with the implementation.`
feat: add docs (#39) * feat: add docs Signed-off-by: Moritz Johner <beller.moritz@googlemail.com> 2021-03-01 07:31:02 +00:00
			`## Cutting Releases`

feat(docs): add proposal process, add bi-weekly meeting 2022-01-22 22:26:59 +00:00			The external-secrets project is released on a as-needed basis. Feel free to open a issue to request a release. Details on how to cut a release can be found in the `RELEASE.md` file in the repo.