See what best practices we can pull out of our work developing inspec profiles. Things to consider include: profile development, structuring projects, creating readmes, etc.

Not sure why this repo needs to be public. Only things in here are some pictures which would be better served to be in sharepoint and then some template files - I think it'd be better to have a proper profile templating process esp considering our intent of adding a more formal testing/release process.

Right now, we assume a Unix runner and access to Git.

Runner differences:
Windows vs Unix

Access issues:
access to Git
no access to Git
access to Git, but need credentials
access to Git, but using MFA

Just realized that bundle and ruby come with the inspec installer for Windows. problem: the path to these isn't automatically set up.

C:\opscode\inspec\bin\ is in the path environment variables
C:\opscode\inspec\embedded\bin\ is not by default.

We should have a table with all our repos maybe separated by baseline, hardening, tools, etc. with links to repos. That way, people can browse all our work in one spot rather than having to search through all our repos.