Closed juliaklindpaintner closed 5 years ago
Some items from the security checklist we need to perform:
I started to write this up as a separate Google doc, but it didn't seem to make sense given that there is actually a lot of content in the repo that should be included in the guide. So I decided to use the project wiki as a home for this.
https://github.com/18F/usda-fns-ingest/wiki
Thoughts, @amymok, @juliaklindpaintner?
Wiki sounds like a good place.
So I've incorporated most of our existing content into the wiki in the usda-fns-ingest
repo. A couple of outstanding issues to highlight:
api.md
doc in the repo, and one that @amymok has been updating in the django-data-ingest repo. Not sure if the difference matters, but if it does we should use the most current version.django-data-ingest
repo that I'm wondering if we should incorporate into the wiki. For example, can we use this overview on customization validation in the FNS wiki?Thank you so much @mheadd . I will definitely try to go over some of those to make updates. I think one thing I have been thinking about as well is, do we actually want to duplicate some of documents from django-data-ingest
to here. Or should we just point to them there? It means potentially everything will get outdated here. But if we are locking down a django-data-ingest
version, maybe it is better to have the outdated doc lives here because we are using that version here.
Any thoughts?
@amymok Yeah, if we're locking down a django-data-ingest
version for the FNS Data Validator, then maybe it makes sense for there to be a separate copy that is tailored to that version.
Thank you for this work, @mheadd! I agree it makes sense to have the separate copy here for FNS that can also build in more language that is specific to their use case and users.
FYSA - I checked off the remaining acceptance criteria because I think we've done them. The guide isn't done, but I think we've finished identifying the sections to be included and incorporated as much of our current content as we can at this point.
Sounds good to me. Let's close this issue.
Overview
As a developer supporting the FNS Data Validation Service, I want to know how to deploy and maintain it so that it continue to be used by FNS after the engagement with 18F is over.
Acceptance criteria