14 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.
I am the developer of source code that has not yet been released.
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.
The following commits were obtained without authorization from a private repository. While the repository was previously public on GitHub, these commits are from after the project Git repository left GitHub and became private.
What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.
The repository should be reverted to the state before these unlawfully obtained commits were pushed otherwise the entire repository should be taken down.
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.
There are no networked forks of this repository.
Is the work licensed under an open source license?
Yes
Which license?
While the source code is under the Mozilla Public License version 2.0 only those elements to build the mail client are being publicly released in Executable Form under that license which would require the source code that went into it to be disclosed. As these stolen patches were obtained without authorization from a private repository not currently hosted on Github no argument over the validity of the patches can be made.
Additionally, the commits relate to a project in the repository that has never been officially released outside of private hands thus until it is the source code changes in question would remain under private copyright until such time an Executable Form was released.
How do you believe the license is being violated?
n/a
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.
There are no other alternatives to resolving this infringement issue.
What would be the best solution for the alleged infringement?
Reported content must be removed
Do you have the alleged infringer’s contact information? If so, please provide it.
Github User/Org ManchildProductions.
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.
[private]
Please type your full legal name below to sign this request.
[private]