Process DMCA request

2022/02/2022-02-23-shellfetch.md

@@ -0,0 +1,111 @@
+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.**
+
+user has changed the licence to something that breaks [private] own
+
+**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]  
+https://github.com/The-Repo-Club/shellfetch
+
+Wrong Licence  
+https://github.com/egor4ka/shellfetch
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/egor4ka/shellfetch
+
+**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.**
+
+there is none at the moment
+
+**Is the work licensed under an open source license?**
+
+Yes
+
+**Which license?**
+
+TRC GENERAL PUBLIC LICENSE  
+Version 3, 31 JANUARY 2022  
+
+This license is an open source license with restrictions for commercial and corporate use.  
+Any project under this license ...  
+CANNOT be used commercially  
+CANNOT be redistributed with any sort of fee  
+CANNOT be redistributed in any proprietary form (binary, obfuscated, etc.)  
+CANNOT be patented  
+CANNOT change to any more proprietary license  
+CANNOT depend on any proprietary code/code blobs/software  
+CANNOT be used by any corporate individual, company or organisation  
+
+DOESN'T have any warranty  
+
+CAN be modified  
+CAN be redistributed in an open source form  
+CAN be used privately  
+
+This license is non-corporate, individual use only.
+
+The owner of this project holds NO LIABILITY if any unstable, redistributed or modified  
+versions of this project harms you in any way.
+
+Redistributed or modified versions of this project...  
+MUST have the same license as the original project  
+MUST disclose the project's source
+
+OWNER: The-Repo-Club <[private]>     
+PROJECT NAME: shellfetch   
+YEAR: 2022  
+
+**How do you believe the license is being violated?**
+
+Changed to GLP3
+
+**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.**
+
+change it back to my licence
+
+**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 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]
+
+**Please type your full legal name below to sign this request.**
+
+[private]