The result is that a lot of developers have had to sign contracts with their employers that say they'll never use or contribute to AGPL code even in their personal time. This is often reinforced by mandatory compliance training that repeats bogus nonsense about how if you ever run an AGPL program on your personal laptop you could turn the entire company codebase into GPL code. These myths then proliferate and end up driving other companies to do the same thing. It's all FUD of course, whether the people repeating it know that or not, but the practical consequences are that a lot of people legally cannot interact with AGPL projects at all. Again, that's not because the license is all that restrictive but because of what amounts to a universal corporate boycott.
Many states also have their own stricter codified procedural protections for disciplining public employees, and of course that's before you get into cop union shit, though obviously the whole premise of the argument here is that we would be changing those state/local rules. But that stuff is a whole other can of worms. I'm just saying that even if you change state/local law/rules, even if you abolish cop unions, any police disciplinary body trying to operate this way they would definitely lose a lawsuit from the first cop they disciplined. I've personally seen multiple fucking volunteer firemen win constitutional due process challenges over getting demoted (like, from assistant chief to secondary assistant chief of what is mostly a social club) because they were disciplined without a formal hearing that afforded them procedural due process.
Unlike parent I'm not saying this is good or that to change it would be "unfair", just that what we're describing here -- that is, making it practically possible to discipline cops -- is disallowed under our current system of laws as we understand it. It would take a variety of substantive changes in how we legislatively and judicially structure procedural rights at every level of government from the top down.