Is it just me or is passing off things that aren’t FOSS as FOSS a much bigger thing lately than it was previously.

Don’t get me wrong. I remember Microsoft’s “shared source” thing from back in the day. So I know it’s not a new thing per se. But it still seems like it’s suddenly a bigger problem than it was previously.

LLaMa, the large language model, is billed by Meta as “Open Source”, but isn’t.

I just learned today about “Grayjay,” a video streaming service client app created by Louis Rossmann. Various aticles out there are billing it as “Open Source” or “FOSS”. It’s not. Grayjay’s license doesn’t allow commercial redistribution or derivative works. Its source code is available to the general public, but that’s far from sufficient to qualify as “Open Source.” (That article even claims “GrayJay is an open-source app, which means that users are free to alter it to meet their specific needs,” but Grayjay’s license grants no license to create modified versions at all.) FUTO, the parent project of Grayjay pledges on its site that “All FUTO-funded projects are expected to be open-source or develop a plan to eventually become so.” I hope that means that they’ll be making Grayjay properly Open Source at some point. (Maybe once it’s sufficiently mature/tested?) But I worry that they’re just conflating “source available” and “Open Source.”

I’ve also seen some sentiment around that “whatever, doesn’t matter if it doesn’t match the OSI’s definition of Open Source. Source available is just as good and OSI doesn’t get a monopoly on the term ‘Open Source’ anyway and you’re being pedantic for refusing to use the term ‘Open Source’ for this program that won’t let you use it commercially or make modifications.”

It just makes me nervous. I don’t want to see these terms muddied. If that ultimately happens and these terms end up not really being meaningful/helpful, maybe the next best thing is to only speak in terms of concrete license names. We all know the GPL, MIT, BSD, Apache, Mozilla, etc kind of licenses are unambiguously FOSS licenses in the strictest sense of the term. If a piece of software is under something that doesn’t have a specific name, then the best we’d be able to do is just read it and see if it matches the OSI definition or Free Software definition.

Until then, I guess I’ll keep doing my best to tell folks when something’s called FOSS that isn’t FOSS. I’m not sure what else to do about this issue, really.

  • lily33@lemm.ee
    9·
    1 year ago

    I didn’t come across any restrictions imposed on an end user to modify the app for their own needs or redistribution

    It’s by default that you can’t redistribute modified versions. You need explicit permission to do so. Furthermore, that license is revocable. So let’s say you invest a lot of time into making modifications - at any point, they can revoke the license, and you suddenly find yourself forbidden from distributing your modified version, too/

    If/when Grayjay is transitioned to FOSS, I imagine it’ll be difficult for the community to maintain it due to the complexity…

    That’s not really relevant. There’s no requirement in open source on how the projects are to be maintained.

    the last thing someone like that would want on a personal project is loads of strangers contributing, bad actors ripping it off trying to make a quick buck, or even worse redistributing it with malware.

    It’s up to him whether he accepts strangers contributing. That has nothing to do with whether it’s open source. If he didn’t want contributions, he could disallow any pull requests on an open source software - or conversely, if there are people willing to contribute to a non-open-source project, there’s theoretically nothing stopping that. Redistributing it with malware is not really a problem open-source projects have, and malware writers wouldn’t care for the license anyway.

    The only thing is would be the somewhat relevant would be making a quick buck part, but that’s only been a problem for people using MIT/BSD license.

    Finally, I’ll never understand why people would want to name software after dental string…