5 ms·

You have the right to use this project via git submodules. The GitHub terms of service requires code owners to allow forking and linking to their public reposit

• DangitBobby 5y ago
  It does not appear to grant (or attempt to grant) use of the software. So sharing and forking are fine, but not necessarily anything else. > 5. License Grant to Other Users > Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. 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). > 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). You may grant further rights if you adopt a license. If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users
  • _t4sy 5y ago
    > 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 submodule is not allowed.
    • 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.