Process DMCA request

This commit is contained in:
dmca-sync-bot 2022-05-18 18:02:15 +00:00
parent b0d630a231
commit d9b648ab21

View File

@ -0,0 +1,155 @@
Before disabling any content in relation to this takedown notice, GitHub
- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
---
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
Yes, I am authorized to act on the copyright owner's behalf.
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
Yes
**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**
1623916
**Does your claim involve content on GitHub or npm.js?**
GitHub
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
I am a [private] at Stanford University and one of the [private] for the [private] course which maintains its materials using the github organization [private]. The copyright for our course materials is held by Stanford University.
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
The original infringing repo was [private]
The repo was owned by [private] [private]
This repo published content and code from our CS107E course that is private to students enrolled in the course.
The specific files of concern in [private] original repo [private] were the files containing solution code for the course assignments. I contacted [private] and requested that he remove these files. He responded to remove the entire repo.
We are now asking to have the forks of his original repo be removed. Removing those entire repos would be acceptable, to instead remove individual files, here is list of the .c files that infringe on our private code:
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
[private]
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repositorys URL.**
The above .c files should be removed from all of the forks below:
https://github.com/blueff/cs107e-review
https://github.com/feng20068/cs107e-review
http://github.com/heqiqi/cs107e-review
http://github.com/holmesmoon/cs107e-review
http://github.com/WenXiangchun/cs107e-review
http://github.com/IAMBANMA/cs107e-review
http://github.com/jasper2007111/cs107e-review
http://github.com/leonardmohr/cs107e-review
http://github.com/rango886/cs107e-review
http://github.com/ruanima/cs107e-review
http://github.com/Sadamingh/cs107e-review
http://github.com/sastar/cs107e-review
http://github.com/stern-hcg/cs107e-review
http://github.com/tangaoo/cs107e-review
http://github.com/tianyuqingkong/cs107e-review
http://github.com/TristenSeth/cs107e-review
http://github.com/wangdepin/cs107e-review
http://github.com/wanliofficial/cs107e-review
http://github.com/wyscjm/cs107e-review
http://github.com/ZhuJunzhe/cs107e-review
http://github.com/zuyeyang/cs107e-review
**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
No
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
Yes, see list of forks above
**Is the work licensed under an open source license?**
No
**What would be the best solution for the alleged infringement?**
Reported content must be removed
**Do you have the alleged infringers contact information? If so, please provide it.**
[private] [private] owned the original repo with the infringing code. He has since removed that repo. We are now asking for the code to also be removed from the forks.
**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
**So that we can get back to you, please provide either your telephone number or physical address.**
[private]
Stanford [private]
[private]
[private]
**Please type your full legal name below to sign this request.**
[private]