|
| 1 | +Before disabling any content in relation to this takedown notice, GitHub |
| 2 | +- 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). |
| 3 | +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). |
| 4 | + |
| 5 | +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). |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** |
| 10 | + |
| 11 | +Yes, I am the copyright holder. |
| 12 | + |
| 13 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 14 | + |
| 15 | +No |
| 16 | + |
| 17 | +**Does your claim involve content on GitHub or npm.js?** |
| 18 | + |
| 19 | +GitHub |
| 20 | + |
| 21 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 22 | + |
| 23 | +I am the [private] and copyright holder of the software project “StellaSoraParser.” [private] wrote and published this code, and [private] [private] all associated copyright to the work. [private] have not granted permission for [private] code to be redistributed without proper attribution or without inclusion of the GNU General Public License (GPL), which is required for reuse. |
| 24 | + |
| 25 | +############# |
| 26 | + |
| 27 | +[private] request that GitHub redact [private] personal identifying information (full name and contact details) from the publicly posted version of this DMCA notice. |
| 28 | + |
| 29 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 30 | + |
| 31 | +The original copyrighted work is [private] software project titled “StellaSoraParser,” which contains code [private] personally created. The infringing repository has copied substantial portions of this code verbatim, including identical file structures and content, without attribution and without including the required GPL license terms. This violates both my copyright and the conditions of the GNU GPL license under which the project is released. |
| 32 | + |
| 33 | +**If the original work referenced above is available online, please provide a URL.** |
| 34 | + |
| 35 | +https://github.com/Hiro420/StellaSoraParser |
| 36 | + |
| 37 | +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** |
| 38 | + |
| 39 | +**Based on the above, I confirm that:** |
| 40 | + |
| 41 | +Specific files within the repository are infringing |
| 42 | + |
| 43 | +**Identify only the specific file URLs within the repository that is infringing:** |
| 44 | + |
| 45 | +https://github.com/shiikwi/fkStellaSora/blob/main/DataBinConvert/StellaSoraParser/YostarGames.cs |
| 46 | +https://github.com/shiikwi/fkStellaSora/blob/main/DataBinConvert/GameController.cs |
| 47 | + |
| 48 | +**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.** |
| 49 | + |
| 50 | +No |
| 51 | + |
| 52 | +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** |
| 53 | + |
| 54 | +**Is the work licensed under an open source license?** |
| 55 | + |
| 56 | +Yes |
| 57 | + |
| 58 | +**Which license?** |
| 59 | + |
| 60 | +gnu-general-public-license-v3.0 |
| 61 | + |
| 62 | +**How do you believe the license is being violated?** |
| 63 | + |
| 64 | +The infringing repository contains direct copies of [private] original code from the “StellaSoraParser” project, but the GNU General Public License (GPL) terms have been removed or not included. The author previously provided attribution but later deleted it entirely. |
| 65 | + |
| 66 | +Under the GPL, redistribution of [private] code is only permitted if the license text is included and full attribution to the original author is preserved. The infringing repository fails to meet these requirements, resulting in a violation of both [private] copyright and the GPL license terms. |
| 67 | + |
| 68 | +**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.** |
| 69 | + |
| 70 | +To bring the repository into compliance with the GNU GPL, the following steps would be necessary: |
| 71 | + |
| 72 | +1. Restore full attribution to [private] as the original author of the code. |
| 73 | +2. Add the complete GNU GPL license text to the repository. |
| 74 | +3. Clearly identify that portions of the code are derived from the original “StellaSoraParser” project. |
| 75 | + |
| 76 | +These actions would satisfy the license requirements and resolve the infringement. |
| 77 | + |
| 78 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 79 | + |
| 80 | +[private] |
| 81 | + |
| 82 | +**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.** |
| 83 | + |
| 84 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 85 | + |
| 86 | +**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.** |
| 87 | + |
| 88 | +**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>.** |
| 89 | + |
| 90 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 91 | + |
| 92 | +[private] |
| 93 | + |
| 94 | +**Please type your full name for your signature.** |
| 95 | + |
| 96 | +[private] |
0 commit comments