jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 11:26:57 -05:00
Code Issues Projects Releases Wiki Activity

Add to forks section - rapid forking, large network

Browse Source
This commit is contained in:
Abby Vollmer
2021-02-18 20:38:38 -08:00
committed by GitHub
parent 8148677058
commit b00ab8e676
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/github/site-policy/dmca-takedown-policy.md
View File

@@ -63,6 +63,8 @@ One of the best features of GitHub is the ability for users to "fork" one anothe
GitHub *will not* automatically disable forks when disabling a parent repository. This is because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by the fair-use doctrine. GitHub does not conduct any independent investigation into forks. We expect copyright owners to conduct that investigation and, if they believe that the forks are also infringing, expressly include forks in their takedown notice.
Please note, if you are alleging copyright infringement in a full repository that is actively being forked and you have identified all known forks at the time or, if the reported network that contains the allegedly infringing content is larger than one hundred (100) repositories, we would consider disabling the entire network if you could state in your notice that, based on the representative number of forks you have reviewed and subsequently listed in your notice, you believe that all or most of the forks are infringing to the same extent as the parent repository.
### C. What If I Inadvertently Missed the Window to Make Changes?
We recognize that there are many valid reasons that you may not be able to make changes within the window of approximately 1 business day we provide before your repository gets disabled. Maybe our message got flagged as spam, maybe you were on vacation, maybe you don't check that email account regularly, or maybe you were just busy. We get it. If you respond to let us know that you would have liked to make the changes, but somehow missed the first opportunity, we will re-enable the repository one additional time for approximately 1 business day to allow you to make the changes. Again, you must notify us that you have made the changes in order to keep the repository enabled after that window of approximately 1 business day, as noted above in [Step A.4](#a-how-does-this-actually-work). Please note that we will only provide this one additional chance.