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.
As a developer, honestly I think this is a good thing.
Open source isn’t always a good thing. It’s not just opening the source, it’s a very specific way to develop software.
In theory, you make something open source, and other devs walk in and out, helping the project grow and helping with admin work. People can tag in and tag out as their schedules allow, and the software will grow organically and democratically, bigger than any single user
In practice, it’s politics. Contributing is rarely on a walk-in basis - but code is your ideas given form, and no amount of power is too little to trip over.
People are protective of their baby, but also don’t want to spend their free time interviewing contributors instead of working on it. And just like mods on top boards, managing a popular open source project attracts a very specific type of person
And finally, we live in a hypercapitalist society right now. Know what happens if you open source a project and it gains traction? Someone runs off and turns it into a service, usually the owner, but not always. Services tend to become the first class citizen, and are free to take investor money and make pull requests to serve their use case at the expense of someone using it themselves.
I think it’s safe to say Linux is the greatest open source project of all time. It’s a clusterfuck that has not lived up to the imagined ideals of open source - I think it’s great and too important to entrust to any group, but it’s a hot mess. And Linus Torvold didn’t open source it for years until it reached a point of maturity.
My point with all this is that OSS is fantastic, but it’s not a virtue intrinsically. After all, almost no one makes money on OSS, but plenty make money on turning such a project into a service.
Opening your source on the other hand? Other people can take bits and pieces to learn from, and people can audit it. If you keep out corporate use, I think that’s fair - I mean, even if you copy code for your own project, you quickly move beyond the 20% difference you need to remove their copyright claim if you’re building something different
I think we need to be more pragmatic about OSS… We need to make multiple philosophies for different people and different types of software
That’s… not a thing. It’s a widely-circulated myth and nothing more. There’s no magical percentage that makes a modified version not a derivative work.
It’s precedent. It’s not law, but it’s not a myth either - it’s a case study we go over with new programmers so they’re not afraid of undeserved lawsuits
Which case(s)?