- Get as much down to unclass as possible, wikis, tickets, code etc.
- This would be a large burden on Mary's team, we can control what we can control, maybe ask Hoff for more resources to support Mary?
- All team members have a udev account
- All team members are part of vpnuser udev group
- All team members have access to a computer that can VPN and VNC
- All team members are in geoint gitlab (interim approach)
- Mirror issues/wiki between geoint gitlab and jira
- Big initial push to work with capturing json definitions of tickets/wiki and getting them downscanned
- Need to figure out what do with gliphy and if our license can be move down
- Would involve writing scripts that interact with gitlab and jira apis
- Potentially move tickets down as part of EBB process
- Same concepts for wiki mirroring
- Big initial push to work with capturing json definitions of tickets/wiki and getting them downscanned
- Testing
- Imagine most of the front end isn't going to work initially
- Initial push is find and squash front end bugs that resulted from messy downscan push
- Document and ticket creation on low side
- Email/slack for communication
- Does CACI have a zoom license?
- Assume a messy hard push to unclass
- Copy existing baseline to a new project
- Clean project (even if it doesn't compile)
- Solve isuses on low side
- Copy cleaned project with no history to final staging and move stanging down
- Get baseline compiling/working on low side and move forward
- Migrate to self hosted gitlab
- Need to understand what features we lose when moving off geoints enterprise gitlab
- Build out Bodhi apps in argocd
- Automate deployment of bodhi apps via argocd and argo workflows
- Setup ldap on govcloud
- Setup vnc servers on udev
- Run vncservers on own box where possible
- Write up wiki for getting developers setup
- If our Atlassian license is based on number of people of Jira/Wiki kick everybody out on the high side, and stand up our own Jira/Wiki on low side...move to something like gitlab for day to day business.