Hi @dnscale-ops !

Welcome to DNSControl! I'm excited to have DNScale added to our list of providers!

• @fm is our “liaison to maintainers”. He'll reach out to you soon.
• I forgot to review the checklist (https://docs.dnscontrol.org/developer-info/writing-providers#step-15-check-your-work) before merging your previous PR. I'm having a busy day, but I'll get to that today or tomorrow. Please use this PR to fill in anything we missed.

Hi @dnscale-ops!

As Tom mentioned I am the Maintainer Liaison. Would you be able to send your contact email to us? You can reach me at dnscontrol at faisal dot fm and Tom at tlimoncelli at stack over flow dot com

Your email will not be public and will only be used the the project team to send out maintainer communications.

As a maintainer, we’d like to remind you of your role and expectations we have so that everyone has a positive experience using dnscontrol:

• Maintainers are expected to support their provider. If a maintainer is no longer able to maintain a provider, they should suggest a replacement or if no replacement is available, the maintainer shall let the maintainer liaison know so they can put out a call for volunteers.
• Maintainers must be responsible to bug reports and PRs for their provider.
• Maintainers should set up test accounts and periodically verify that all tests pass (pkg/js/parse_tests and integrationTest), especially when new features are added or changed in the core product.
• Contributors are encouraged to add new tests and refine old ones. (Test-driven development is encouraged.)

Thank you!!

Hi @dnscale-ops!

As Tom mentioned I am the Maintainer Liaison. Would you be able to send your contact email to us? You can reach me at dnscontrol at faisal dot fm and Tom at tlimoncelli at stack over flow dot com

Your email will not be public and will only be used the the project team to send out maintainer communications.

As a maintainer, we’d like to remind you of your role and expectations we have so that everyone has a positive experience using dnscontrol:

• Maintainers are expected to support their provider. If a maintainer is no longer able to maintain a provider, they should suggest a replacement or if no replacement is available, the maintainer shall let the maintainer liaison know so they can put out a call for volunteers.
• Maintainers must be responsible to bug reports and PRs for their provider.
• Maintainers should set up test accounts and periodically verify that all tests pass (pkg/js/parse_tests and integrationTest), especially when new features are added or changed in the core product.
• Contributors are encouraged to add new tests and refine old ones. (Test-driven development is encouraged.)

Thank you!!

@fm, @tlimoncelli - thank you for reaching out. https://docs.dnscontrol.org/developer-info/writing-providers#step-15-check-your-work followed through, output of the integration tests is attached. Email with contact email has been sent over.

dnscale_integration_logs.zip

@tlimoncelli, could you please create the GitHub label provider-DNScale?

@tlimoncelli, could you please create the GitHub label provider-DNScale?

Done! (https://github.com/StackExchange/dnscontrol/issues?q=state%3Aopen%20label%3Aprovider-DNSCALE)