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.

  • p_q@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    8
    ·
    edit-2
    7 months ago

    free

    open source ≠ free

    open source ≈ source code published

    it’s free software

    • lily33@lemm.ee
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      7 months ago

      That’s not the accepted usage of the term, though. Rather, open source = free software.

      And while I do like the term free software better, I don’t think trying to start war on which term to use would help anything.

      • p_q@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        5
        ·
        7 months ago

        free software is relevant

        open source is only one point and can also apply to properity software

        • jack@monero.town
          link
          fedilink
          arrow-up
          3
          arrow-down
          2
          ·
          7 months ago

          open source is only one point and can also apply to properity software

          What makes you think that?

        • lily33@lemm.ee
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          7 months ago

          You can technically can your proprietary software “free” too. But that’s not what the term means. And nether does “open source”.

          • p_q@lemmy.world
            link
            fedilink
            arrow-up
            2
            arrow-down
            4
            ·
            7 months ago

            you can do much with free software. depending on the licence, also unfree software. but then it’s no free software anymore

    • TootSweet@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      3
      ·
      7 months ago

      When I use the term “Open Source” I mean [the OSI definition]https://opensource.org/osd/), which is what the term meant from its inception. If you want to talk about “source code published” software, use a different term. Don’t appropriate “Open Source” or think you’re representative of the Open Source community.

      When you say “free” here, do you mean this or something else?

      • p_q@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        7 months ago

        seems like someone tried to solve a problem by declaring

        open source ≈ freesoftware

        You can compile a binary by using the provided code and it gives you a binary, yes.

        you modify the code, compile, sell the binary, because “they provided the code” opensours.org said “it means free software” “free as in freedom” so “I am free to do whatever I want with this software.” "

        That is untrue. I can open source my product for a reason, but if anyone try to sell it it’s a crime. I openenly show everyone my source code, but without the right licence it’s nothing. often you can’t even compare it to the software running.

        • FooBarrington@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          That is untrue. I can open source my product for a reason, but if anyone try to sell it it’s a crime. I openenly show everyone my source code, but without the right licence it’s nothing. often you can’t even compare it to the software running.

          No, that’s not true. If you open source your product, anyone else can sell it just fine. They can’t do so if you don’t open source it (i.e. if you make it source available).

          Just because you think “open source” means “source available” doesn’t mean they are legally equivalent.