• sweng@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    1 day 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
      1
      arrow-down
      2
      ·
      1 day 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 day ago

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

            • chebra@mstdn.io
              link
              fedilink
              arrow-up
              0
              arrow-down
              3
              ·
              1 day ago

              @sweng

              Look, I can’t help you if you don’t even read the things you are posting. 🤷‍♂️

              • sweng@programming.dev
                link
                fedilink
                arrow-up
                4
                ·
                1 day 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
                  0
                  ·
                  16 hours 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

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

                    Why on earth would the license use Github’s very niche definition? “Forking” as a software concept has been around for decades longer than Github or it’s “fork” button has existed.

                    Also, how about reading the full psragraph?

                    You may not create, maintain, or distribute a forked version of the software.

                    (emphasis mine). It only does what you think it does if forking = copying. Which it doesn’t.

                    Question to you: Github provides a button labeled “Download ZIP” for downloading a .zip-file containing the source. If I press that button, am I in your opinion creating a fork?