Process DMCA request

2024/04/2024-04-03-university-of-manchester.md

@@ -0,0 +1,98 @@
+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 the copyright holder.
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
+
+No
+
+**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.**
+
+[private] is in the readme.md, and [private] appear as the [private] at the course unit public website [private]
+
+You can contact [private] at [private]. He is involved in the [private], [private], and [private].
+
+**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.**
+
+[private]
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/henggao98/Event_Lite
+
+**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.**
+
+No.
+
+**Is the work licensed under an open source license?**
+
+Yes
+
+**Which license?**
+
+BSD licenced including copyright statement on Copyright 2017-2024 [private], [private]
+
+**How do you believe the license is being violated?**
+
+This repository (https://github.com/henggao98/Event_Lite) is a coursework Computer Science students take at the [private] as part of the Software Engineering 2 course unit ([private]). The original work is available at [private] (which is password-protected). The coursework is conducted in teams, and the repo's main branch is forked in our internal [private] instances (these repos are password-protected).
+
+Students are told they cannot publish their work on public repositories because:
+
+- It enables collusion.  
+- It infringes copyright. The Intellectual Property Policy of The University of Manchester is available at [private]
+
+When it comes to Teaching materials and the rights in teaching materials, (see Section 5) of the policy indicates:
+
+"IP in Teaching Materials created, made and/or developed by an Employee during the course of
+their employment shall belong to the University in accordance with the normal rule set out at
+paragraph 3.3 and the rights set out in paragraphs 4.2 and 4.3 shall continue to apply."
+
+That is, the IP belongs to the university.
+
+**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**
+
+Making the repository private.
+
+**What would be the best solution for the alleged infringement?**
+
+Repository can be made private
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+I emailed the alleged infringer at [private] as this was included in some commits of other public projects. The alleged infringer is an alumnus of the university, but I am still waiting for a reply to my email asking to set the repository as private.
+
+**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]  
+[private]  
+[private]  
+[private]  
+[private]  
+
+**Please type your full legal name below to sign this request.**
+
+[private]