It depends on the contract. In the DOE system it's usually national lab employees working under direct funding; in that case the operating contractor retains copyright. In the DOD world it's more common for development to be actual USG employees, in which case there is no copyright and the software is public domain.
None of this applies to state or local government: 17 USC 105 applies only to federal matters.
Attribution tends to be important to DOE people since they're usually academics working in the purview of Office of Science, and citations are how they get promoted.
I don't think anyone worries about AI training on their codebases, since LLM providers are not held accountable to any copyright enforcement anyway.
You misunderstood my point about govt software contractors needing to worry about AIs being trained on their codebases: for their job security, automating and replacing them. Specifically, if the govt tries to do the same things we see in commercial SW devpt.
(Not copyright claims against commercial LLM companies).
None of this applies to state or local government: 17 USC 105 applies only to federal matters.
Attribution tends to be important to DOE people since they're usually academics working in the purview of Office of Science, and citations are how they get promoted.
I don't think anyone worries about AI training on their codebases, since LLM providers are not held accountable to any copyright enforcement anyway.