> Open source doesn't just mean access to the source code.
is pretty good evidence they themselves are to blame for poorly picking the terminology. You can't really fault people for assuming words mean what they say and not going back to check the etymology. Consider it a special case of designing intuitive UIs. Which is something many pieces of software (especially open-source software...) don't do particularly spectacularly.
It's kinda like picking your site to be called "Hacker News" and then yelling at people for thinking that's where the hackers that broke into their computers got their news. The associated trouble and confusion is the price you decided to pay in exchange for picking a cool (but misleading) name.
As far as the terminology goes, keep in mind that the people defending the OSI are generally the people or at least in line with the people that coined and popularised the terms and their continued usage, and while that may seem like an easy way to dismiss certain talking points it's a point that's going to keep being brought up in response to the argument of feigned ignorance to the terms, and I don't mean this to come across as too mean but something like open source has 20 years of mindshare, free software 30 years, more broad but still applicable terms like open access 40 years, or the greater cultural undercurrent much longer than that. At a certain point even the most well meaning individuals who are looking at existing open source licences and creating their own with the express intention of avoiding commercial exploitation[0], a problem almost exclusive to open source licenced software, are going to recognise that what they're doing isn't entirely in line with the existing open source ethos, and I don't think it's unfair or entirely unexpected that people will point out that it's not part of the open source ethos.
[0] From the licence: 'Under no circumstances shall the Person be permitted, allowed or authorized to commercially exploit the Software.', but other similar and more fleshed out licences might make the connection to open source software being exploited more explicit.
> The loan adjective "libre" is often used to avoid the ambiguity of the word "free" in English language, and the ambiguity with the older usage of "free software" as public-domain software.
https://en.wikipedia.org/wiki/Free_software#Naming_and_diffe...
Flagging you for calling names isn't harassing. Familiarize yourself with rules of this community. (Flagging comments you disagree with that doesn’t break any site guidelines — now that is harassment.)
> I'm sick of self-proclaimed "orgs" (with unclear sponsorship) or SJWs claiming ownership of commonly used terms.
This is revisionist history. OSI was formed and OSD was published in February 1998 immediately after the term "open source" was proposed, and OSD was largely based on Debian Free Software Guidelines which predates the term.[1][2] So the term only became popular after the "self-proclaimed org" formed and popularized it. The OSD clearly predates any so-called open source abuse, and AFAIK it was never revised due to some sort of corporate sponsorship.
You can coin your own term and try to popularize it. FSF has their free software (well, that's actually a weak claim on a broad term) and libre software (much better). You can also get behind some weird term like "Open Source with Commons Clause", or just use another commonly used term, "source available" (which, granted, spans a pretty wide range on the restrictiveness spectrum, so definitely not ideal).
Meanwhile, many of us get annoyed when commercial products try to reap the marketing benefits of open source but does not grant the rights we've come to expect from the term. This particular case isn't even subtle like the Commons Clause.
[1] https://opensource.org/history
[2] https://en.wikipedia.org/wiki/History_of_free_and_open-sourc...