Hacker News new | past | comments | ask | show | jobs | submit login

RMS should think about this form of delivery in GPLv4. j/k



I personally wouldn't mind the GPL being revised to disallow weapons of war using the code.


First, do you really think people creating weapons of war would bother obeying the GPL?

And secondly, that would result in the GPL no longer being complaint with the Open Source Definition[1], which does not allow "field of endeavour" restrictions. Whether or not the FSF cares about that point is questionable (I doubt they care much) but it could make life more difficult for F/OSS developers in general.

[1]: http://oreilly.com/catalog/opensources/book/perens.html


The FSF have what seems like a well-considered position on such things: http://www.gnu.org/licenses/hessla.html


True, and just to be clear, when I said "I doubt they care very much" I meant "I doubt they care very much about not being compliant with the OSD." It does, of course, make sense that they make have a position that overlaps with a point from the OSD, for their own reasons.


I do suppose it would be better to just be able to force them to obey the GPL (and distribute their code), than disallow them to use it.


There are sometimes operational difficulties in 'forcing' the owner of a nuclear armed carrier battlefleet to obey anything.

It's even worse than trying to force a teenager to tidy their room!


I have to agree with the general principle of this. Hanging on my sister's kitchen wall is a tea-towel printed with a record of a delightful conversation between US and Canadian forces. They each insist the other should divert course. The US forces describe what they are - a carrier group, and again insist that the Canadian forces divert course. The Canadian forces simply reply, "This is a lighthouse." ;)

With all that said, I don't think it applies to licenses at all. Licenses are paperwork. Do I need to say more?


It isn't about the armed forces themselves, as they rarely make their own arms. Most weapons companies are publicly traded corporations.


First, do you really think people creating weapons of war would bother obeying the GPL?

Sure, most weapons of war are created by companies which act within the law in order to do so.

A broader question is: I don't think you can revise the GPL, can you? If you change the GPL it's no longer the GPL referred to by the GPL when the GPL says that anything produced with the GPL must be licensed under the GPL, thus all existing GPL software will still be under the old GPL not the new GPL.

You'd have to start from scratch with a new licence and develop a new codebase.


The FSF publishes new revisions (see: GPLv3). Some projects are released strictly under GPLv2 (e.g. Linux), but it's more usual to release software under "... or, at your option, any later version published by the Free Software Foundation".


Some weapons of war require custom code, but for those systems that can use COTS software, you would rather see them use Windows and possibly other commercial software, rather than linux/*bsd and their F/OSS ecosystems?

I don't think that would accomplish much except hurt the DOD and hurt open source software that various parts of the DOD contribute to.


That would go directly against freedom zero, and criteria 6


But weapons used for defence are still cool, right?


That has come up a few times and there is a non-military clause for creative commons. IIRC it was in the code for a digital radio system.

But even assuming the bad guys would abide by it - it gets tricky:

Does the police count? What about SWAT teams, what about the FBA, the CIA?

Is the coastguard part of the Navy in your country? Does that make SAR "military"? Could they use it only on rescue missions but not on law enforcement?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: