199
submitted 11 months ago* (last edited 11 months ago) by TootSweet@lemmy.world to c/opensource@lemmy.ml

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.

you are viewing a single comment's thread
view the rest of the comments
[-] captain_aggravated@sh.itjust.works 15 points 11 months ago

Something akin to the Creative Commons Share-alike non-commercial license?

[-] theshatterstone54@feddit.uk 4 points 11 months ago

Yeah, basically one of the CC licenses (probably this one, I don't know CC that well) but for software. It's been a license I dream of and have dreamt of for a while. I guess the closest we have is the GPL but eben rhat has been bypassed.

[-] MigratingtoLemmy@lemmy.world 2 points 11 months ago

Oh, maybe that? Can that be applied to code?

[-] captain_aggravated@sh.itjust.works 7 points 11 months ago

Not directly.

Though I'd kinda like to talk to a lawyer about the viability of a license whose terms are something like

This software is furnished free of charge for use or study for any purpose other than shareholder profit. Use or study of this software for any purpose that would benefit businesses supported by shareholders is strictly prohibited.

Because I've got code I wouldn't mind some folks who are selling art on Etsy or making games on itch.io using, but I'll be throatfucked before I'd let Amazon or Facebook have it.

[-] toastal@lemmy.ml 4 points 11 months ago* (last edited 11 months ago)
[-] MigratingtoLemmy@lemmy.world 3 points 11 months ago

Ah unfortunately, I'm not very good with licensing. But any license that can achieve what I mentioned would be perfect. I just want the authors of such software to be able to distribute their code without being fucked over by major corporations

[-] toastal@lemmy.ml 4 points 11 months ago

Beware that these licenses are not compatible with GPL. You would have to dual-license or rely just on ISC, MIT, etc. types of licenses for libraries since GPL doesn’t allow you to restrict based on industry or business model. We would need a larger pool of copyfair or copyfarleft licensed code to have a reasonable pool of code in the Commons to pull from for free software but a lot of it is GPL.

this post was submitted on 20 Nov 2023
199 points (93.1% liked)

Open Source

31129 readers
295 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS