• chebra@mstdn.io
    link
    fedilink
    arrow-up
    8
    ·
    1 month ago

    @sweng

    > you agree to allow others to view and “fork” your repositories

    How did you come to the conclusion that this does not grant the permissions to fork? It’s literally in the sentence. Where else did you find the definition of “forking”, if not here? This is what Github defines in the TOS, this is the label on the button in github UI, so clearly this is also what winamp means when they forbid “forking” and that means it’s against the TOS. There is no other “forking”.

    • sweng@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 month ago

      I got it from the TOS:

      By setting your repositories to be viewed publicly, you agree to allow others to view and “fork” your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).

      They explicitly define it as making copies. There is no mention of being allowed to modify said copy. Also note the quotes around “fork”, since it differs from the usual definition.

      E.g. wikpedia (https://en.m.wikipedia.org/wiki/Fork_(software_development) defines it thusly:

      In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software.

      (Emphasis mine)

      • chebra@mstdn.io
        link
        fedilink
        arrow-up
        2
        ·
        1 month ago

        @sweng But what else would “forking” mean? As you said “in the usual sense”. This is the usual sense - making a copy of the repo on github = forking.

        • sweng@programming.dev
          link
          fedilink
          arrow-up
          5
          ·
          1 month ago

          I edited my reply to include the definition from Wikipedia, but there are of course many other sources.

                • sweng@programming.dev
                  link
                  fedilink
                  arrow-up
                  4
                  ·
                  1 month ago

                  How about you continue reading a bit further, until you hit the word “and”.

                  take a copy of source code from one software package and start independent development

                  (emphasis mine).

                  Github defines “forking” as just copying, while normally it is understood as copying + further development (creating a “fork” in the development history, hence the name).

                  • chebra@mstdn.io
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    1 month ago

                    @sweng No need, I can instead continue reading the “license” and see the word “or”.

                    > You may not create, maintain, or distribute

                    They disallow creating copies. Plus other things, but already creating the fork by either definition is disallowed. Not to mention, wikipedia is not a legal document while the TOS is, the double-quotes are used because that’s the first time a new term is used, followed by its definition, and that the license is likely using Github’s definition, not wikipedia’s