Edits to "fork" definition #65
Merged
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
Providing clarification of language related to “fork” definition. As recommended here: #53
wking
reviewed
Jul 27, 2017
wking
left a comment
There was a problem hiding this comment.
It may also be worth pointing out that for some repositories forking may not be allowed by the license or law. The current ToS include a grant for the right to fork for public repositories, but this section does not make that private/public distinction, and with #54 or similar the ToS would no longer include that grant (allowing you to publicly host all-rights-reserved content on GitHub).
Policies/dmca-takedown-policy.md
Outdated
| ### B. What About Forks? (or What's a Fork?) | ||
|
|
||
| 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](/articles/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork. | ||
| One of the best features of GitHub 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 on GitHub into their own repositories. As the license or the law allows, Users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[fork](/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.
I think you want to keep “users” (which you're currently changing to “Users”), because it is not defined locally in this document:
$ git grep Users origin/pr/65 -- Policies/dmca-takedown-policy.md
origin/pr/65:Policies/dmca-takedown-policy.md:One of the best features of GitHub 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 on GitHub into their own repositories. As the license or the law allows, Users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[fork](/articles/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork.
Thanks for the contribution, @wking!
Contributor
Author
|
Thanks again for the contributions @evandrocoan and @wking! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Providing clarification of language related to “fork” definition. As
recommended here: #53
/cc @evandrocoan Thanks!