Review and revise existing GitHub content

[arouault]

Goal: Develop collaboration tool skills and staff capacity

Measure of Success:

• [x] right people in the room
• [x] retro yields action toward future publishing
• [x] clear owner (Vermonter) to own that work
• [x] github value is internalized

Next Steps:

• [x] Conduct meeting with Vermont staff (Cass, Devon, Amy, who else?) on communications strategies to work in the open, use of Github moving forward.
• [x] Possibly make part of the Roadmapping work?
• [x] Making sure everyone has a github account
• [x] Streamline content, add additional features
• [x] Publish tech principles and other updated content to github (with Vermonters)

[arouault]

@SeamusLoftus Add Cass to github organization @arouault ping on email

[arouault]

Go to @AmyMarshallCarney / @DevonDowning to get approved tech principles published.

[arouault]

Remaining to-dos from Cass:

• [x] North Star
• [x] Add in list with links to product descriptions and charter language
• [x] Include Technical Principles
• [x] Include programs in scope in description
• [x] Table of contents
• [x] Cass to rewrite "we've changed our approach" section
• [x] change landing page content
• [x] Alicia to send devon list out missing information from roadmap
• [x] Alicia to format benefits table
• [x] update roadmap and publish it
• [x] devon to upload the rest of the PDFs for charters

Later on

• [ ] Have Dixie/Randy write up something on procurement strategy
• [ ] Eventually, have steven and seamus round out tech strategy with devsecops
• [ ] Eventually include KPIs in product descriptions

[arouault]

Updates still being made by Devon before 1/1.

[arouault]

Look into github pages as a way to communicate information / more user friendly.

[arouault]

Final changes submitted for review