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?
Yes
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 [private] of the ebook this notice is about.
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.
[private] ebook "Professional CMake: A Practical Guide" is only legitimately available from [private] website. You can find it at https://crascit.com/professional-cmake/
Copies of the ebook are not allowed to be made available to anyone other than the purchaser.
What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.
That file was added by commit [private], which needs to be removed from that repository.
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, although a legitimate version of the file should contain details of the purchaser at the bottom of each page. The PDF has been modified to remove those details.
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.
The following forks also contain the offending commit with the same commit hash and therefore an unauthorised copy of the work:
Is the work licensed under an open source license?
No
What would be the best solution for the alleged infringement?
Reported content must be removed. Either remove the commit from the git history or remove the entire repository (the file is not an authorized copy in any of the repositories).
Do you have the alleged infringer’s contact information? If so, please provide it.
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]