this post was submitted on 01 Feb 2024
70 points (96.1% liked)
Open Source
31276 readers
746 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've always felt that public money should require public code. It makes total sense, unless you are a politician who wants to give favors and earn kickbacks.
Sane way that publicly funded science should be published and freely accessible.
It's a pipe dream, coz capitalism.
Capital interests certainly oppose the public domain, but I don't think it's a pipe dream, I think it's a policy change. Everything has swung in favor of private capital for long enough that it's time for the pendulum to swing back toward the public interest. I think the iron is hot, and right now is the time to start imaging and building better institutions.
Things are definitely moving in this direction, a number of changes at the federal level are happening in the US. The US and EU have many grant/funding programs where open publishing is a requirement, not an option.
Absolutely, and I'm glad someone else has thought the exact same thing! "Public money == public code".
When the government contracts for IT equipment, it comes with terms about maintenance, updates, and life cycle. It would require a much higher cost, especially in FTE funding, to ensure that open source code is viable and safe before deployment. I'm not implying that there are zero risks or errors with contracts, though they do provide some benefits.
It takes the same amount of time to develop closed source as open source software. So doea validating and certifying it.
Not sure why it should be more expensiv to put the moeny towards a OSS solution.
Because the government would have to hire the employees directly for this, versus the company that is contracted to do so.
No. You can write in the contract that the Software needs to be open.