3 ms·
.. no? I mean, is the Microsoft Visual Studio Community license a "wink, wink" license? Or the Sun Community Source License? Or the Atlassian Community License?
by eesmith 8y ago
.. no? I mean, is the Microsoft Visual Studio Community license a "wink, wink" license? Or the Sun Community Source License? Or the Atlassian Community License?
FWIW, "Community" in the license name seems to indicate "not free software" and "not open source software". There's only one OSI or FSF approved license with that word in the name.
They write 'Strictly speaking it is “source-available.”' That description has its own Wikipedia page. https://en.wikipedia.org/wiki/Source-available_software https://en.wikipedia.org/wiki/Source-available_software points out that it doesn't always meet "the criteria to be called open-source".
- anilgulecha 8y agoNo one I know of treats MSVS or Atlassian or whatever is under SCSL as open source. Confluent was treated and used as open source and that changed.
- deleted 8y ago[deleted]
- eesmith 8y agoI understand that it changed. But if there is a "wink, wink", who is it supposed to be for? For those who knew it was F/OSS? If so, it's not very effective, since they know the difference, and the text is clear that about why it's not likely to be considered F/OSS by the OSF, FSF, or Debian. Or is it a "wink, wink" to those who didn't know? In which case, don't the many other community-but-not-F/OSS licenses mean that Confluent is being consistent with what others do? AS someone who hasn't used Confluent but knows about issues related to F/OSS licensing and the difficulties of getting sufficient funding for developing F/OSS software, the explanation was pretty much what I expected for a company switching to an open core model from one which was all open source. So, why might it be a "wink, wink"? That's likely my stumbling block in understanding your g'parent comment.