Eddie Knight

Currently working through confirming the items on the "passing" checklist: ## Basics ### Basic project website content - [x] The project website MUST succinctly describe what the software does (what...

A strategy has not yet been implemented for unique version numbering: > The project results MUST have a unique version identifier for each release intended to be used by users.

Releases are not yet part of the CFI lifecycle, though that could easily be established with a bit of planning

Until we finish migrating the structure to a module-based structure (#239) we will not be able to finish the following reuirement: > The project MUST clearly show or document how...

Working with Bob today to identify action items necessary to complete the checklist above. The next comment from Bob should contain our notes and suggested next steps, which we _may_...

Progress on the badge application can be seen by org and repo maintainers: https://bestpractices.coreinfrastructure.org/en/projects/6557/edit#changecontrol

Submitted with the release and version items marked as unmet/pending

We will be creating a new repo, and will use that repo's issue tracker for individual work items related to this effort

@AdrianHammond, would you care to update this issue with next steps (or a plan) to finalize the IaC for this effort? Additional commenters are welcome as well :+1:

@AdrianHammond will provide a summary of the design, which will implement Ansible to orchestrate the sequential terraform processes.