Completed the fork definition #53
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Copied from: 1. https://help.github.com/articles/dmca-takedown-policy/#b-what-about-forks-or-whats-a-fork The definition of what a GitHub fork means. Currently the ToS only states that fork is a bare copy of a GitHub repository. However as defined on the referenced article, a fork means also the users can make changes to their copy, instead of get them as read-only copies. Related issues: 1. github#7 OSS licences vs. ToS: grants of rights 1. github#37 The term "fork" is not defined anywhere in the GitHub Terms of Service 1. github#38 More permissive license grant to other users
This was referenced Jul 18, 2017
mirabilos
reviewed
Jul 18, 2017
| 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). | ||
|
|
||
| One of the best features of [Git](https://git-scm.com/book/en/Getting-Started-Git-Basics) is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project and then make changes to that copy to either push back to the main project or just keep as their own variation of a project. We call each of these copies a "[fork](https://help.github.com/articles/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork. | ||
|
|
There was a problem hiding this comment.
Do note that the “fork”s in which users have made changes may not be redistributable to anyone else.
Contributor
|
👋 Hi @evandrocoan, thanks for pointing out that discrepancy between the DMCA policy description and our Terms of Service. While the DMCA policy was not intended to convey any rights to or from users, we can see how the description of a "fork" could be somewhat confusing when compared to its definition in the Terms of Service. Therefore, in order to clear up any confusion, we'll be updating the DMCA policy language to reflect the definition in the Terms. Thanks again! |
bluemazzoo
added a commit
that referenced
this pull request
Jul 26, 2017
Providing clarification of language related to “fork” definition. As recommended here: #53
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Copied from:
The definition of what a GitHub fork means. Currently the ToS only states that fork is a bare copy of a GitHub repository. However as defined on the referenced article, a fork means also the users can make changes to their copy, instead of get them as read-only copies.
Related issues: