Sure but it is also part of the author's own freedom to choose what his software is used for.
A lot has been talked about the restrictions of open source.
If I want my program used for things I agree with only I should have that right. If OSI says my license isn't good, then I'll be proud to have a non-conforming license.
You have the right to do what you want with your copyrighted intellectual property. Nobody disputes that. Just don't call whatever you want "open source" when it isn't.
If I want my program used for things I agree with only I should have that right. If OSI says my license isn't good, then I'll be proud to have a non-conforming license.
The OP talked of "open sourcing". This implies that his software will satisfy freedom 0 - which is not possible with a military use restriction.
EDIT: If he just meant "releasing the source code" he would surely have used this wording.
Comments
Sure but it is also part of the author's own freedom to choose what his software is used for.
A lot has been talked about the restrictions of open source.
If I want my program used for things I agree with only I should have that right. If OSI says my license isn't good, then I'll be proud to have a non-conforming license.
You have the right to do what you want with your copyrighted intellectual property. Nobody disputes that. Just don't call whatever you want "open source" when it isn't.
The OP talked of "open sourcing". This implies that his software will satisfy freedom 0 - which is not possible with a military use restriction.
EDIT: If he just meant "releasing the source code" he would surely have used this wording.