From d6c1e654c9bd6151884223714ee88c7072f307c9 Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Fri, 25 Aug 2023 20:37:45 +0000 Subject: [PATCH] Process DMCA request --- .../2023-08-24-carnegie-mellon-university.md | 84 +++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 2023/08/2023-08-24-carnegie-mellon-university.md diff --git a/2023/08/2023-08-24-carnegie-mellon-university.md b/2023/08/2023-08-24-carnegie-mellon-university.md new file mode 100644 index 000000000..1eb573003 --- /dev/null +++ b/2023/08/2023-08-24-carnegie-mellon-university.md @@ -0,0 +1,84 @@ +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.** + +2286008 + +**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 authorized via my employment at Carnegie Mellon University to act on behalf of the copyright holders. + +**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 work comprises code (in both object and source form) which has been developed as part of the [private] course at Carnegie Mellon University, as well as example test cases and auxiliary build system files. + +The entire contents of the `boards/` and `lib/` directories, as well as the files Makefile, README.txt, are components of the original work(s) which appear unmodifed in the infringing repository. `board-ht.h`, `lightsout` and `lightsout-d` are derivative works of either a different original work or other content identified above as infringing in the repository. In order to remedy the infringement, those files would need to be removed. + +**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.** + +https://github.com/mpai227/Lightsout-Solver/blob/master/boards/ +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/boardutil.h +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/contracts.h +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/heap.c +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/heap.h +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/hset.c +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/hset.h +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/queue.c +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/queue.h +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/xalloc.c +https://github.com/mpai227/Lightsout-Solver/blob/master/lib/xalloc.h +https://github.com/mpai227/Lightsout-Solver/blob/master/board-ht.h +https://github.com/mpai227/Lightsout-Solver/blob/master/lightsout +https://github.com/mpai227/Lightsout-Solver/blob/master/lightsout-d + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +No + +**Have you searched for any forks 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.** + +The infringing repository has no forks. + +**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 infringer’s contact information? If so, please provide it.** + +**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 fair use 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 Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +I can be reached at [private]. + +**Please type your full legal name below to sign this request.** + +[private]