Live data from Hacker News

Project includes a dependancy that has a license that forbids its use

github.com

141–150 of 249 posts

Re: Project includes a dependancy that has a license that forbids its use

#141
post #129

Earlier quoted context omitted.

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 repositories, regardless of license.

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" y…

> 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.

Re: Project includes a dependancy that has a license that forbids its use

#142
post #107

Copyright Bouke van der Bijl I do not give anyone permissions to use this tool for any purpose. Don't use it. I’m not interested in changing this license. Please don’t ask.

If it keeps this out of production in even a handful of companies, that's probably a good thing in aggregate.

It's a neat blog post, shows interesting internals, and no - you should not do it.

Re: Project includes a dependancy that has a license that forbids its use

#143
post #25

I love that all the discussion here is about the license I wrote and not about the actual project, which is a completely terrible idea and something I created as a lark. Why did I not spell this out in the blog post? For my own amusement. I also think it shows that licenses really don't matter all that much as some people think, they are not computer code.

That's because this thread is specifically about the license.

Re: Project includes a dependancy that has a license that forbids its use

#144
post #141

Earlier quoted context omitted.

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" y…

> 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.

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?

Re: Project includes a dependancy that has a license that forbids its use

#145
post #141

Earlier quoted context omitted.

> 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.

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?

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.

Re: Project includes a dependancy that has a license that forbids its use

#146
post #145

Earlier quoted context omitted.

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?

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 & G…

> 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.

Re: Project includes a dependancy that has a license that forbids its use

#147
post #25

I love that all the discussion here is about the license I wrote and not about the actual project, which is a completely terrible idea and something I created as a lark. Why did I not spell this out in the blog post? For my own amusement. I also think it shows that licenses really don't matter all that much as some people think, they are not computer code.

Someone posted the actual project here: https://news.ycombinator.com/item?id=28266515 - but since both the url and the title of the OP are specifically about the license, it's not surprising that that was the topic.

Re: Project includes a dependancy that has a license that forbids its use

#148
post #145

Earlier quoted context omitted.

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 & G…

> 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.

> 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

Re: Project includes a dependancy that has a license that forbids its use

#149
post #145

Earlier quoted context omitted.

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 & G…

> 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.

[deleted]

Re: Project includes a dependancy that has a license that forbids its use

#150
A long time ago I implemented a similar (less flexible) thing for C, also as a sort of goofy learning experience:

https://github.com/mgraczyk/fast_check_once/blob/master/fast...

There's something really appealing about replacing code at runtime to "hack" the bypass normal behavior of the language. For testing/mocking this can even be useful.

Post reply on HN