-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update gov.txt directly from zone #118
Comments
@h-m-f-t - in Fireside, we reviewed this and wanted your feedback on the actual priority on this item. It's fairly high in the backlog now. |
It's true this isn't super urgent. However, one of my reasons for it being high in the backlog is that it is similar to the work recently done to archive the CZDS zone file and so it may be easy to pick up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #107, we updated gov.txt (a copy of the zone file_ each day from the version we publish each day to CZDS. Instead of pulling once daily from a copy, we should pull from our DNS provider, Cloudflare, which we could also poll more frequently since the provenance of the data is the real source. Let's start with once every 6 hours.
One question to answer is our commit approach. We want to see the individual commits but summarize them into one (like a PR, though we don't want to need to approve a PR).
Acceptance criteria
Additional Context
The text was updated successfully, but these errors were encountered: