Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Some, but probably not all. Seems like it would be a bad move to open-source all military software.
Why? Open source only requires sharing the source when sharing the software. No distribution of software - no distribution of source. But if they are gonna sell software to other militaries or civilian contractors, we have a right to know what they're selling.
And no, hiding your code doesn't generally make your software more secure.
It just seems like a bad tactic. For example, if the US gives Ukraine some software that helps them fight Russia, it's likely tactically advantageous (to Ukraine) if Russia doesn't have the source code.
Of course, it doesn't mean Russia couldn't do some reverse engineering to some extent. But that takes time, and likely wouldn't be as complete/thorough as just handing them the source code.
If the DoD gives some ooen source software to Ukraine they are required to give the source code to Ukraine - not to Russia.
Trying to understand what you're saying: how is that open source then? It sounds like you're saying giving the source to Ukraine only would suffice.
That's exactly what I'm saying. Go read the GPL and you'll see that's what it says too.
You’re confusing GPL with open source. Not all open source software is GPL.
The general discussion in this thread is if source code to government software should be publicly available. Not if government software should adopt GPL.
Its not just GPL. MPL, BSD work this way as well. And the original post refers to open source, not "code available to all". Come back with a commonly used open source license that enforces what you're describing and maybe you'll have a point. Otherwise, why are we arguing about things that can just be looked up?
It’s generally not a good idea to make military technology accessible to the enemy.
So you didn't read my comment before replying?
that could be solved by encrypted military plugins/addons that have their own security measures