mirror/stackexchange-dnscontrol
1
0
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-05-11 05:55:12 +00:00
Code Issues Releases Activity

Update docs and move Azure Private DNS to the "community support" list (#2657)

Browse Source 
Co-authored-by: Matthew Gamble <mgamble@mgamble.ca>
This commit is contained in:
Tom Limoncelli
2023-11-28 16:28:37 -05:00
committed by GitHub
parent 37e21030a2
commit 5b93f94ad6
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
documentation/providers.md
View File

@ -76,7 +76,6 @@ Providers in this category and their maintainers are:
|Name|Maintainer|
|---|---|
|[`AZURE_DNS`](providers/azure_dns.md)|@vatsalyagoel|
[[`AZURE_PRIVATE_DNS`](providers/azure_private_dns.md)|@matthewmgamble]
|[`BIND`](providers/bind.md)|@tlimoncelli|
|[`CLOUDFLAREAPI`](providers/cloudflareapi.md)|@tresni|
|[`CSCGLOBAL`](providers/cscglobal.md)|@mikenz|
@ -95,16 +94,18 @@ provided to help community members support their code independently.
Expectations of maintainers:
* Maintainers are expected to support their provider and/or find a new maintainer.
* Maintainers are expected to support their provider and/or help find a new maintainer.
* Maintainers should set up test accounts and periodically verify that all tests pass (`pkg/js/parse_tests` and `integrationTest`).
* Contributors are encouraged to add new tests and refine old ones. (Test-driven development is encouraged.)
* Bugs will be referred to the maintainer or their designate.
* Maintainers must be responsible to bug reports and PRs. If a maintainer is unresponsive for more than 2 months, we will consider disabling the provider. First we will put out a call for new maintainer. If noboby volunteers, the provider will be disabled.
* Maintainers must be responsible to bug reports and PRs. If a maintainer is unresponsive for more than 2 months, we will consider disabling the provider. First we will put out a call for new maintainer. If nobody volunteers, the provider may be disabled.
* Tom needs to know your real email address. Please email tlimoncelli at stack over flow dot com so he has it.
Providers in this category and their maintainers are:
|Name|Maintainer|
|---|---|
[[`AZURE_PRIVATE_DNS`](providers/azure_private_dns.md)|@matthewmgamble]
|[`AKAMAIEDGEDNS`](providers/akamaiedgedns.md)|@svernick|
|[`AXFRDDNS`](providers/axfrddns.md)|@hnrgrgr|
|[`CLOUDFLAREAPI`](providers/cloudflareapi.md)|@tresni|

2
documentation/writing-providers.md
View File

@ -316,7 +316,7 @@ Here are some last-minute things to check before you submit your PR.
2. Make sure all appropriate documentation is current. (See [Step 8](#step-8-manual-tests))
3. Check that dependencies are current (See [Step 13](#step-13-dependencies))
4. Re-run the integration test one last time (See [Step 7](#step-7-integration-test))
5. Re-read the [maintainer's responsibilities](providers.md) bullet list. By submitting a provider you agree to maintain it, respond to bugs, perioidically re-run the integration test to verify nothing has broken, and if we don't hear from you for 2 months we may disable the provider.
5. Re-read the [maintainer's responsibilities](providers.md) bullet list. By submitting a provider you agree to maintain it, respond to bugs, periodically re-run the integration test to verify nothing has broken, and if we don't hear from you for 2 months we may disable the provider.
## Step 16: After the PR is merged