3 ms·

> So sharing and forking are fine, but not necessarily anything else. Did I imply otherwise? Git submodules are just links. Please explain how linking to a sub

• DangitBobby 5y ago
  Well, I thought the purpose of linking in git submodules was to compile the source code and then use it. The "using it" is not granted by the GitHub license. Did I misunderstand your original point? If not, the verbiage "use this project via git submodules" which uses the word "use" was the source of my confusion. Was someone disputing the right of OP to share a link to the blog post or the repository?
  • _t4sy 5y ago
    You said it yourself: GitHub users can use GitHub projects on GitHub. Git submodules stay on GitHub, so it's allowed. > you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking) You can run the code on GitHub Codespaces & GitHub Actions, you can fork the code to make changes, and you can dynamically link/embed the code in other projects on GitHub through git submodules.
    • DangitBobby 5y ago
      > You can run the code on GitHub Codespaces I think this would fall under "use" which I dispute the GitHub TOS allows. > and you can dynamically link ended the code in other projects on GitHub through git submodules. Sure. As long as you do not compile and run it, you can link it until you turn blue in the face.
      • _t4sy 5y ago
        > As long as you do not compile and run it, you can link it until you turn blue in the face. With GitHub Codespaces and GitHub Actions you aren't compiling or running the code, GitHub is. From my understanding, this satisfies the following: > solely on GitHub as permitted through GitHub's functionality
        • DangitBobby 5y ago
          I don't really know much about CodeSpaces but yeah, if it is always run in a service provided by the GitHub ecosystem, you can probably run it. I don't know how useful that is. Also, it says you can fork it. It does not say you can modify it.
        • chrisoverzero 5y ago
          I told the judge that I didn’t kill anyone, the hitman I hired did! For some reason, he didn’t see it as you do.
          • hansvm 5y ago
            Performing those actions on GitHub isn't important because it allows you to technically bypass a restriction by having a third party do it (which I agree is a poor defense) but because the author explicitly relinquished some rights by putting the project on GitHub.
            • iamevn 5y ago
              the author does not relinquish rights to run the code. running it on a third party service does not magically launder the license.
              • hansvm 5y ago
                > does not relinquish the rights to run the code I don't think anyone who's posted so far is a lawyer, but the claim is precisely that GitHub's ToS do relinquish the rights to run the code, so long as you only do so on GitHub and through their published interface. GitHub ToS> If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). > running it on a third party service does not magically launder the license Totally agreed. By uploading to GitHub publicly you've granted an _additional_ license and asserted that you had the legal right to do so. It's kind of like when open source projects will also sell a proprietary license on request -- companies aren't magically beholden to the GPL'd version just because it exists somewhere; they get to choose which of their available licenses they'd prefer to use.
      • deleted 5y ago
        [deleted]