If it is not using and OSI-approved license and claims to be open source it is open washing. Call it shared source or something else.
This is a long since settled debate.
- only grants the right "to access and use the code solely for the purposes of review, compilation and non-commercial distribution."
- only grants the right "provide the code to anyone else and publish excerpts of it for the purposes of review, compilation and non-commercial distribution"
- "you are not entitled to use or do anything with the code for any commercial or other purpose, other than review, compilation and non-commercial distribution"
This breaks all 4 freedoms the free software definition and at least aspects 1,3,4 and 6 of the OSD.
From a legal POV, this project is unforkable. You are not allowed to modify this in any way (even just for your own use).
Furthermore, you are not even allowed to use this internally (unmodified and without ever distributing it). I am not even sure it is possible to legally be a user of the software for its intended purpose. The license states clearly that "other than review, compilation and non-commercial distribution" you "are not entitled to use or do anything" and that includes using the compiled result to watch videos. This is about as restrictive as the MS-RSL.
Basically, the only thing you can do with it is archive it and look at it. (and wait lifetime + 70 years until it becomes public domain)
Proprietary software and closed source refer to the same thing.
Most people you've interacted are wrong. sorry...
Maybe there's some hidden point you're trying to make by associating these concepts but it'd be easier if you said it plainly.
Other than that I think you find that people in real life don't tend to be exact in their use of language all the time, and calling understandable imprecisions "wrong" tends to decrease the number of friends you get.
The history of the term is very clear. The term was coined by Christine Peterson in a group session in 1998 with Todd Anderson, Larry Augustin, Jon Hall, Sam Ockman, Michael Tiemann, and Eric S. Raymond. Months later the OSI was created by the same people in order to manage that definition. There is nothing unclear here. "Open source" is defined by OSI and it has been defined by them from the very start.
If communities let others distort words, those words loose their meaning. As a well known example, the word "woke" which has long been abandoned by the community that coined it.
"Open source" is an actively defended term by the organisation that originally defined it and the community around them.
The web is full of HTML, CSS, and JavaScript you can see the source for; and for which you can be sued by copying for your own commercial gain. By your definition, websites are open source; and yet, they are proprietary work. Something having its source open doesn’t make it Open Source.
This kind of doublespeak reeks of Reddit-grade corporate astroturfing.
The Open Source licenses are defined and protected in a certain way. You can’t just say “oh, me and my friends don’t think of it like that” and expect to be correct. I can’t build an app scamming people out of currency by abusing ISO 4217, and then excuse myself under “me and the people I know disagree with ISO”. OSI protects the licenses, the Vegan Society certifies what ‘vegan’ means, ISO does ISO things, and so on.
It’s okay to admit we’re wrong or ignorant, so I won’t pretend I’m an expert in this area. I also wouldn’t call anyone Stallman just because they are defending a term that deserves protection. “Source available” but not under the terms of an OSI license is NOT compliant with the term.
I'm sorry, I thought it was obvious.
As "proprietary software" and "closed source" refer to the same it wouldn't be logical to use the opposite "open source" to refer to "proprietary software".
People don't have to be exact in their language, the point is for the other to understand what you mean.
I consider it the most polite and the most constructive to use the definition from the believers themselves.
Academic, as in relating to education and scholarship. Anarchy, as in without Archons. Archons, as in leaders of ancient Greek city-states. Let the communist define what it is, let the socialist, let the Jew, let the ufologist etc
There is the Open Source Initiative, the page starts with what they consider Open Source. https://opensource.org/osd/
Besides practicality the website also states: Never use or register any trademarks that are confusingly similar to, or a play on, the OSI or OSI Logo. An example of unacceptable is given: "Open Source Project"
EDIT: See https://www.gnu.org/philosophy/open-source-misses-the-point....
Microsoft gave up and now only calls OSI-approved licenses open source.
Open Source means OSI-approved.
If you can read the source code but it's not OSI-approved, than it's source-available or shared source or something else.
OSI isn't authoritative of the term.
Regardless of what other uses the word open has/had, "open source" was defined by OSI and they are authoritative over the term.
If I define climate neutral as climate positive, climate neutral doesn't become climate positive nor do I get authority of the term climate neutral.
Some terms were defined by a community and their use defended. Others were defined by a community, appropriated by others, distorted by others and subsequently abandoned by the original community. And yet others, were abandoned and then reclaimed by the original community.
"Open Source" is in the first category, defined by OSI and defended by the FLOSS community. It is actively being defended, and fish much bigger than you have failed to topple the community.
Nope it's what you and OSI try to do.
Is this a hill you really want to die on?
It doesn’t matter at all.
The “can see code” = “must be open source” argument is stupid because it’s entirely opinion based. You cannot be right about it.
It depends what you choose to define “open source” as. If you define it as some arbitrary thing (eg. I can read the source code) then of course you’re right. …but you can’t force other people to accept your arbitrary definition.
You can only have an opinion about it.
Same as anyone else.
Is it really worth the argument?
Source available is unambiguous, being explicit (“source can be download from GitHub”) I means you don’t have to waste your time on arguments like this for, what seems, truely trivial reasons.
How does it?
"Source available is unambiguous"
It's not, because it could be hidden behind a pay wall.
But you may call source-available software whatever you want, just not open source unless it's under and OSI-approved license.
You can use any words other than the phrase "open source" to be as unambiguous as you want.
If you feel it’s not explicit enough be more explicit (source is available from xxx of you login or whatever).
If you want a legal opinion, get a lawyer, that’s what they do.
If you just want to do what’s “normal”, take a successful project (eg. Unreal) and do what they do.
It seems like a total non issue.