4.6 KiB
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.
- provided information on how to submit a DMCA Counter Notice.
To learn about when and why GitHub may process some notices this way, please visit our README.
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.
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.
This is a folder backup tool. The repository URL is https://github.com/SO-TS/but. The open source license used is Mozilla Public License 2.0. The organization it belongs to is [private] SO-TS. [private] belong to the organization.
What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.
https://github.com/MCSeekeri/but
Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.
No
Have you searched for any forks 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 forks.
Is the work licensed under an open source license?
Yes
Which license?
Mozilla Public License 2.0
How do you believe the license is being violated?
This is a folder backup tool. The repository URL is https://github.com/SO-TS/but. The open source license used is Mozilla Public License 2.0. The infringer forked the repository at https://github.com/MCSeekeri/but, and later submitted a PR to the original repository, but it was closed. Afterwards, the infringer cloned the repository and turn all the commits into a single commit with his own signature, using the GNU Affero General Public License. This repository has a series of violations of the open source license: the new license is not mentioned in the MPL-2.0 sublicensable license, no documentation is provided for modifications to the source code, and the source code has no copyright information.
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.
Add copyright information, add change description, modify open source license to Mozilla Public License 2.0.
What would be the best solution for the alleged infringement?
Other Change
Describe the change.
Add copyright information, add change description, modify open source license to Mozilla Public License 2.0, contact us for settlement
Do you have the alleged infringer’s contact information? If so, please provide it.
Email: [private]
[private]
[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 fair use 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 Guide to Submitting a DMCA Takedown Notice.
So that we can get back to you, please provide either your telephone number or physical address.
Phone: [private]
Please type your full legal name below to sign this request.
[private]