Fork/review code.gov

[lukefretwell]

Test site

https://codecagov.z22.web.core.windows.net

To-do

• fork code.gov
• make fork public (in CDT organization: https://github.com/CDTgithub)
• set up test environment for review (related: resourcing assessment)
• review workflow
• discuss assessment

Related: #26

[lukefretwell]

@BettyJablonsky @abquirarte documenting code.gov fork review/conversations here. @cwkummer once you accepted repo invite, can you assign this to yourself?

[abquirarte]

Documenting Update from 3/25: @Michael-Hanley

We’ve made 3 contributions back to the fed for code.gov that are currently under review.

o 1 Bug fix

o Lots of automated tests

o Official Banner feature that was requested on Slack

· Automated Testing

o Ryan has been working to get test coverage up and was able to get us above 90% on the front end.

§ We’ve developed these tests for code.gov and once they’re approved we’ll pull them into our project also.

· ADA

o I’ve ran all pages through two different screen reader extensions in chrome in addition to the site improve extension.

§ Made improvements based on the flow of screen readers.

§ Made edits based on suggestions from site improve.

o In addition Myself, Chris Eddy, and Ryan Vollmer are all signed up to take a web accessibility course and we hope to use this training to improve the site further.

· Feature

o We’ve created a registration work flow POC that should simplify the ability of state entities to sign up and have created a couple options of how it can work.

§ We’re hoping this will help with Governance of the platform.

· Architecture

o Working with Eric to get our base environment setup.

o I have moved ElasticSearch out of our Docker App Service for reliability and scalability

· Policy and Governance

o Chris Eddy and I have spent some time brain storming and we have tried to figure out what we can come up with to ensure the security of our code and the platform.

§ We are trying to make how the system works as clear as possible and have compiled a list of questions that we hope will guide a 2 and a half hour discussion we have scheduled for tomorrow on how we can implement this.