Skip to content

Commit ebf1489

Browse files
Merge pull request #18099 from github/updates
Added 2025/07/2025-07-01-source-code.md
2 parents 2b33556 + 1c8b288 commit ebf1489

File tree

1 file changed

+101
-0
lines changed

1 file changed

+101
-0
lines changed

2025/07/2025-07-01-source-code.md

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
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+
[private] the [private] [private] and copyright holder of the source code published under the EternalCodeTeam organization on GitHub. [private] created the code and licensed it under GPL-3.0.
24+
25+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
26+
27+
The original work is Java code for a Minecraft server plugin system and utilities developed by [private] and published under the EternalCodeTeam GitHub organization. The work includes configurations, services, command systems, player management, and utility classes used in Minecraft Paper plugins. The projects are fully original and published under the GNU GPLv3 license.
28+
29+
**If the original work referenced above is available online, please provide a URL.**
30+
31+
https://github.com/EternalCodeTeam/EternalCore
32+
https://github.com/EternalCodeTeam/EternalCodeCommons
33+
34+
**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.**
35+
36+
**Based on the above, I confirm that:**
37+
38+
The entire repository is infringing
39+
40+
**Identify the full repository URL that is infringing:**
41+
42+
https://github.com/BX-Team/Nexus
43+
https://github.com/BX-Team/commons
44+
45+
**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.**
46+
47+
No
48+
49+
**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:**
50+
51+
**Is the work licensed under an open source license?**
52+
53+
Yes
54+
55+
**Which license?**
56+
57+
gnu-general-public-license-v3.0
58+
59+
**How do you believe the license is being violated?**
60+
61+
The GPL-3.0 license requires that any derivative or copied code:
62+
- includes the original license file,
63+
- credits the original authors,
64+
- remains open-source under the same GPL-3.0 license.
65+
66+
The repository https://github.com/BX-Team/Nexus copies substantial code from [private] projects without:
67+
- including the GPL license,
68+
- providing attribution to the original authors (EternalCodeTeam),
69+
- releasing the code under a compatible license (it appears proprietary or unlicensed).
70+
71+
This is a direct and serious violation of the GPL-3.0 terms.
72+
73+
**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.**
74+
75+
To comply with the GPL-3.0 license, the repository owner must:
76+
- add clear attribution to the original authors (EternalCodeTeam),
77+
- include the original GPL-3.0 LICENSE file in the root of the repository,
78+
- ensure that their repository is also licensed under GPL-3.0 (or a compatible license),
79+
- optionally provide a notice of changes if the code has been modified.
80+
81+
If they are unwilling to do so, the repository should be removed from GitHub.
82+
83+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
84+
85+
No, I do not have contact information for the alleged infringer.
86+
87+
**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.**
88+
89+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
90+
91+
**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.**
92+
93+
**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>.**
94+
95+
**So that we can get back to you, please provide either your telephone number or physical address.**
96+
97+
[private]
98+
99+
**Please type your full name for your signature.**
100+
101+
[private]

0 commit comments

Comments
 (0)