News for hackers. Stuff that matters.

A comment on Automatic1111 is back on GitHub after removing Embedding Links. Parent comment

Re:Automatic1111 is back on GitHub after removing Embedding ... by vageli on Thursday January 05, 2023 @01:21PM (#34264114)
> 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.

https://docs.github.com/en/site-policy/github-terms/github-t...

[ Parent | on HN ]
Re:Automatic1111 is back on GitHub after removing Embedding ... by fpgaminer on Thursday January 05, 2023 @01:26PM (#34264183)
I read that as saying that all public GitHub repos can be copied and republished on GitHub, but that doesn't include the right to _modify_ the code. The latter could only be granted by a license. Of which, there is none on Auto's work. And there's none known for any of the work of other contributors.

So while you can "fork" it, it's not forking it in the FOSS sense.

[ Parent | on HN ]