4 ms·
I am in support of it too, ultimately, but after working on federal government software projects, it is a very huge uphill battle. Consider this: your trying t
by GabeIsko 3y ago
I am in support of it too, ultimately, but after working on federal government software projects, it is a very huge uphill battle.
Consider this: your trying to build a grants management system for Defense contractors in Afghanistan. You want to make sure that public money is not going to terrorists sanctioned by the US government. There is a forensic accounting software platform widely used by firms that audit the banking industry,but it is closed source and sold to firms commercially. Should the government spend money on making new software or license the existing software that works extremely well? Should the configuration for what the government creates on that software be open to the public, and open to competitors to imitate? Should they demand that the source code is released? Also what about national security?
Would AWS release all their source code to retain their largest customer, the US government?
I agree that the amount of closed source software used in government projects is staggering and a legitimate barrier to government IT working properly. But the broken process that governments spend money is a bureaucratic nightmare. I am not sure their would be technical downsides, but absolutely their are political ones.
The only thing that I could imagine being an actual downside is the retention of confidential information in the interest of national security or public trust. That is a political minefield already, and open source code can help with security, so I don't even think that is the largest hurdle.
- burnished 3y agoSeems like in your example they should make or buy as they see best fit, but if they make they should make it public. If it could conceivably be a military secret then I expect it would be exempt. I don't see anything about copyleft style policies here which you seem to be referencing heavily, where are you getting that from?
- GabeIsko 3y agoBut that is how the government operates - what is the point of requiring the government to have all the software they develop be open source when they are contracting out all software development to contractors that develop on proprietary platforms? It's not like the government is hiring software engineers in a meaningful capacity, at least not the US government.
- burnished 3y agoI don't know what to tell you (tried and failed to get a number for programmers employed by the USG, its enough that they have a reputation for not paying as well as private sector), but it sounds like you made up a requirement and got mad about it?
- GabeIsko 3y agoI'm not mad. But if your goal is to open source code and software developed with taxpayer money, its not as straightforward as this initiative makes it out to be.
- bombolo 3y ago> Would AWS release all their source code to retain their largest customer, the US government? Yes. Companies would comply with whatever requirement to have the US government as a customer.
- GabeIsko 3y agoThey could sue, they could drop them as a client and not bid, they could offer reduced services like they already do with gov cloud, there are a lot of ways this could play out. Apple has shown that private corporations aren't ready to blindly comply with the US government if it doest suit their business interests.
- bombolo 3y agoApple wasn't selling to the US government. They just received a request from a tribunal. There was no money for them in that. Completely different situation.