Even *more* interesting is that they have a link from the sign-in page to a FAQ at:
https://public.sites.disa.ecs.mil/ecs/git-mil-faq/
A few highlights & commentary:
Q; Who can use
git.mil?
A: Git.mil is available to any Department of Defense (DoD) employee with a current Common Access Card (CAC). Login is federated to the existing DoD Office365 accounts. If you are having trouble authenticating to the application, please try to self enroll in the federation tenant using this link. Accounts should be automatically provisioned but sometimes errors prevent their federation.
That is REALLY WEIRD because it doesn't say if DoD *contractors* with CACs can use it. If contractors can't use it, that makes it much less useful. However, if they're starting with employees, and then at some point will expand to others with a CAC, that would be sensible.
Q: What is the approved classification for data storage in
git.mil?
A: Controlled Unclassified Information (CUI). Git.mil is not approved to store HIPAA or PII. So please keep those out.
Actually, that's better than I expected. Many projects can live with that.
Q: Who can I contact for support on
git.mil?
A: Support for this service is very limited. For basic questions and troubleshooting, please contact
disa...@mail.mil.
That's rather lame. I understand that they're afraid to make many commitments, but that would be rather off-putting for real work.
Q; What does it cost to use
git.mil?
A: The service is currently free to DoD users.
That, at least, is a good thing.
Q: What software does
git.mil run?
A: Git.mil runs gitlab software. Git.mil is running on kubernetes in a 10k user reference architecture. If you would like access to the specific design, please contact
disa...@mail.mil
This makes sense to me. In particular, running GitLab (which is COTS) instead of some weird bespoke software is a good sign.
---- David A. Wheeler