Today FUTO released an application called Grayjay for Android-based mobile phones. Louis Rossmann introduced the application in a video (YouTube link). Grayjay as an application is very promising, but there is one point I take issue with: Grayjay is not an Open Source application. In the video Louis explains his reason behind the custom license, and while I do agree with his reason, I strong disagree with his method. In this post I will explain what Open Source means, how Grayjay does not meet the criteria, why this is an issue, and how it can be solved.

  • rglullis@communick.newsOP
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    The point is super simple: if the author of Grayjay has any provision in the license saying anything to the effect of “you can only redistribute this under certain conditions”, then it’s not Open source as defined by OSI. You may not agree with it and you might fully support Grayjay’s opinion, it doesn’t change the fact that it. is. not. open. source.

    • t3rmit3@beehaw.org
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      1 year ago

      Can you please link to where on opensource.org it says that? This just sounds like your or a general community interpretation. I don’t see that in writing anywhere.

      I literally quoted their website NOT saying what you claim, and your only response is, “nuh uh, it’s what I said.”

        • t3rmit3@beehaw.org
          link
          fedilink
          arrow-up
          5
          ·
          edit-2
          1 year ago

          Thank you, that is a good find. The other person I’ve been talking to hasn’t been able to cite anything from them. I’ve updated my top-level comment with this info.

          Interestingly, I wonder if they distinguish commercial use from commercial distribution, which the author is talking about. Not allowing someone to use the software as a business is very different from not allowing them to sell it as a product.

          edit: Reading more into this, I do think this is about prohibiting use of software by commercial entities, not prohibiting entities from selling the software.

          • hiddengoat@kbin.social
            link
            fedilink
            arrow-up
            7
            ·
            1 year ago
            1. Non-commercial and ethical clauses. These are commonly seen attempts to restrict licenses in violation of OSD 6, “No Discrimination Against Field of Endeavor.” These types of clauses limit where, why and how the software can be used.

            It’s that simple. Any attempt to restrict who can use the software, and how they can use it, renders it OSD incompatible. Chiefly, with this:

            1. No Discrimination Against Fields of Endeavor
              The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
            • t3rmit3@beehaw.org
              link
              fedilink
              arrow-up
              4
              ·
              edit-2
              1 year ago

              Yes, but using software is different than distributing it. Running code on my computer vs selling it.

              If I tell a business, “hey, I don’t like capitalism, so you can’t install the software”, that’s very analogous to the other ethical clauses they’re talking about (usually clauses that prohibit use by LEOs and military). There is a clause about redistribution (1), and it expressly specifies that it applies to “aggregate software distribution containing programs from several different sources”, not single, standalone works.

              • cacheson@kbin.social
                link
                fedilink
                arrow-up
                3
                ·
                1 year ago

                There is a clause about redistribution (1), and it expressly specifies that it applies to “aggregate software distribution containing programs from several different sources”, not single, standalone works.

                That is a weird way of wording it. In practice I doubt there are any OSI-approved licenses that prohibit standalone commercial distribution. If there were, you could trivially comply by just including a “hello world” program to make it an aggregate distribution.