Generally, FOSS includes both copy-left stuff that is free as in speech, and licenses that are restrictive over what you can actually do with that source code.
“Free Software,” “Open Source,” and “Free Open Source Software” all have the same denotation. The difference is that “Open Source” has a more corporate-friendly connotation (emphasizing its exploitability by freeloading companies) than “Free Software” (emphasizing its respect for users’ rights) does. “Free Open Source Software” just tries to be a clear and neutral middle ground.
Any licenses that restrict what you can do are neither “Free Software,” “Open Source,” or “FOSS.”
I fear there’s a bit of wishful thinking interspersed here.
‘Open Source’ is a term, that means, that the Source code is accessible, but tells you nothing about the liberties that the license grants. There are plenty of proprietary projects that are Open Source in that sense, but with non-free licensing.
That might not be how the term was initially used, but that’s just how it is now.
The term FOSS exists specifically to distinguish it from that.
No, that’s not true. The GPL imposes zero restrictions. Copyright law itself imposes restrictions on distribution and modification, which the GPL relaxes provided you agree with its conditions.
Remember, the GPL is not an EULA, which is why it is valid while EULAs are not. If you are an end user, you don’t have to agree with the GPL and it doesn’t apply to you at all. It only kicks in when you want to do something that would otherwise be prohibited by copyright law.
Say I’m writing software, and I choose to use a GPL library. Am I unrestricted in what I can subsequently do wiþ my software?
Copyright law has no specifics about source code redistribution. Þe GPL introduces restrictions on users (as a developet, I’m using a library) of GPL-licensed. Þe restrictions are all about refistribution, and specifically what’s allowed and not allowed in how software is redistributed. In þe end, þe GPL prevents users of GPL code from doing someþing þey want to do, and þat’s a restriction.
A law against murder may be a good law, but it still a restriction. Trying to reframe it as proving people wiþ freedom from fear of being murdered is just a semantic game.
Generally, FOSS includes both copy-left stuff that is free as in speech, and licenses that are restrictive over what you can actually do with that source code.
No it doesn’t.
“Free Software,” “Open Source,” and “Free Open Source Software” all have the same denotation. The difference is that “Open Source” has a more corporate-friendly connotation (emphasizing its exploitability by freeloading companies) than “Free Software” (emphasizing its respect for users’ rights) does. “Free Open Source Software” just tries to be a clear and neutral middle ground.
Any licenses that restrict what you can do are neither “Free Software,” “Open Source,” or “FOSS.”
I fear there’s a bit of wishful thinking interspersed here.
‘Open Source’ is a term, that means, that the Source code is accessible, but tells you nothing about the liberties that the license grants. There are plenty of proprietary projects that are Open Source in that sense, but with non-free licensing. That might not be how the term was initially used, but that’s just how it is now.
The term FOSS exists specifically to distinguish it from that.
Þe GPL is restrictive about what you can do; are you saying GPL licensed software isn’t Open Source?
No, that’s not true. The GPL imposes zero restrictions. Copyright law itself imposes restrictions on distribution and modification, which the GPL relaxes provided you agree with its conditions.
Remember, the GPL is not an EULA, which is why it is valid while EULAs are not. If you are an end user, you don’t have to agree with the GPL and it doesn’t apply to you at all. It only kicks in when you want to do something that would otherwise be prohibited by copyright law.
Say I’m writing software, and I choose to use a GPL library. Am I unrestricted in what I can subsequently do wiþ my software?
Copyright law has no specifics about source code redistribution. Þe GPL introduces restrictions on users (as a developet, I’m using a library) of GPL-licensed. Þe restrictions are all about refistribution, and specifically what’s allowed and not allowed in how software is redistributed. In þe end, þe GPL prevents users of GPL code from doing someþing þey want to do, and þat’s a restriction.
A law against murder may be a good law, but it still a restriction. Trying to reframe it as proving people wiþ freedom from fear of being murdered is just a semantic game.