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.

  • TootSweet@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    …20% difference you need to remove their copyright claim…

    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.

    • theneverfox@pawb.social
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      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

        • theneverfox@pawb.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Ultimately this. I believe the 20% came from a lower court opinion, but search sucks these last few months so I can’t find exactly what I was looking for

          At the end of the day 20% different isn’t the actual standard, it’s more complicated than that. But it’s what we tell fresh developers so they have a baseline - they’re almost certainly safe at that point, and more importantly they feel safe to build things with a hard line like that

          Ultimately, the supreme Court decided the case on a more fundamental level (so the % didn’t come into play at all)