Updated Contribution Guide TOC

This commit is contained in:
Petros Kolyvas 2020-04-03 16:04:55 -04:00
parent 942b4df545
commit ca90de14ec
1 changed files with 10 additions and 6 deletions

View File

@ -13,10 +13,12 @@ To record a bug report, enhancement proposal, or give any other product feedback
<!-- MarkdownTOC autolink="true" --> <!-- MarkdownTOC autolink="true" -->
- [Contributing Fixes](#contributing-fixes)
- [Proposing a Change](#proposing-a-change) - [Proposing a Change](#proposing-a-change)
- [Caveats & Areas of special concern](#caveats--areas-of-special-concern) - [Caveats & areas of special concern](#caveats--areas-of-special-concern)
- [State Storage Backends](#state-storage-backends) - [State Storage Backends](#state-storage-backends)
- [Provisioners](#provisioners) - [Provisioners](#provisioners)
- [Maintainers](#maintainers)
- [Pull Request Lifecycle](#pull-request-lifecycle) - [Pull Request Lifecycle](#pull-request-lifecycle)
- [Getting Your Pull Requests Merged Faster](#getting-your-pull-requests-merged-faster) - [Getting Your Pull Requests Merged Faster](#getting-your-pull-requests-merged-faster)
- [PR Checks](#pr-checks) - [PR Checks](#pr-checks)
@ -85,6 +87,8 @@ For code that has a listed maintainer or maintainers, the Terraform team will hi
There is no expectation on response time for our maintainers; they may be indisposed for prolonged periods of time. Please be patient. Discussions on when code becomes "unmaintained" will be on a case-by-case basis. There is no expectation on response time for our maintainers; they may be indisposed for prolonged periods of time. Please be patient. Discussions on when code becomes "unmaintained" will be on a case-by-case basis.
If an an unmaintained area of code interests you and you'd like to become a maintainer, you may simply make a PR against our [CODEWONERS](https://github.com/hashicorp/terraform/blob/master/CODEOWNERS) file with your github handle attached to the approriate area. If there is a maintainer or team of maintainers for that area, please coordinate with them as necessary.
### Pull Request Lifecycle ### Pull Request Lifecycle
1. You are welcome to submit your pull request for commentary or review before it is fully completed. Please prefix the title of your pull request with "[WIP]" to indicate this. It's also a good idea to include specific questions or items you'd like feedback on. 1. You are welcome to submit your pull request for commentary or review before it is fully completed. Please prefix the title of your pull request with "[WIP]" to indicate this. It's also a good idea to include specific questions or items you'd like feedback on.