Skip to content

Commit a22b2d6

Browse files
Merge pull request #18094 from github/updates
Added 2025/06/2025-06-30-moslem-tools.md
2 parents 6c47fc6 + 54845bc commit a22b2d6

File tree

1 file changed

+93
-0
lines changed

1 file changed

+93
-0
lines changed

2025/06/2025-06-30-moslem-tools.md

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
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 [private] to the "Moslem Tools" software project. [private] [private] the majority of the source code, especially the full database structure, backend logic, and uploaded over 11,000 unique JSON files. The infringing repository was originally forked from [private] shared project and includes substantial content that [private] created. Despite this, the other party has removed [private] name and falsely claimed sole ownership.
24+
25+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
26+
27+
The original copyrighted work is a software project named "Moslem Tools", which was jointly developed to assist Muslim users with accessing Islamic texts, audio recitations, and daily utilities. [private] personally developed the core of the application including the database schema, more than 11,000 JSON resource files, the backend structure, and substantial parts of the user interface logic. The code was originally hosted on GitHub and represents months of work. [private] contributions can be clearly seen in the original repository’s commit history, which shows [private] authored over 284 commits and added more than 35 million lines, compared to the other developer’s ~129 commits.
28+
29+
**If the original work referenced above is available online, please provide a URL.**
30+
31+
https://github.com/mesteranas/moslemTools_GUI
32+
33+
**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.**
34+
35+
**Based on the above, I confirm that:**
36+
37+
The entire repository is infringing
38+
39+
**Identify the full repository URL that is infringing:**
40+
41+
https://github.com/mesteranas/moslemTools_GUI
42+
43+
**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.**
44+
45+
No
46+
47+
**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:**
48+
49+
https://github.com/mesteranas/moslemTools_GUI
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 GPLv3 license requires that all original copyright notices and proper attribution to authors be preserved. The infringing repository removed [private] ([private]) entirely from the README, the license file, and the source code headers, despite my substantial contributions (284 commits, over 35 million lines of added content, including all major database and backend files). The project was copied and republished without any mention of [private] authorship, violating both the attribution and license inclusion requirements of GPLv3. This presents the work as entirely authored by the other contributor, which is inaccurate and against the license terms.
62+
63+
**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.**
64+
65+
To bring the repository into compliance with the GPLv3 license, the following changes are required:
66+
67+
1. Add full and visible attribution to [private] ([private]) in the README file, LICENSE file, and source code headers where appropriate.
68+
2. Restore acknowledgment that this is a derivative of our joint work, including a clear reference to [private] repository.
69+
3. Include the GPLv3 license file if not already present.
70+
4. Remove any false claims of sole authorship.
71+
5. If these conditions cannot be met, the repository should be taken down entirely to stop the misrepresentation and license violation.
72+
73+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
74+
75+
GitHub Username: mesteranas
76+
Infringing Repository: https://github.com/mesteranas/moslemTools_GUI
77+
I do not have their personal email address or physical contact information.
78+
79+
**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.**
80+
81+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
82+
83+
**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.**
84+
85+
**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>.**
86+
87+
**So that we can get back to you, please provide either your telephone number or physical address.**
88+
89+
[private]
90+
91+
**Please type your full name for your signature.**
92+
93+
[private]

0 commit comments

Comments
 (0)