Skip to content

Commit a70e6c9

Browse files
Merge pull request #12817 from github/updates
Added 2023/02/2023-02-02-ccs.md
2 parents b8b0dc6 + 6cd2fcf commit a70e6c9

File tree

1 file changed

+69
-0
lines changed

1 file changed

+69
-0
lines changed

2023/02/2023-02-02-ccs.md

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
2+
3+
Yes, I am the copyright holder.
4+
5+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
6+
7+
Yes
8+
9+
**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**
10+
11+
9ED5PQ-
12+
13+
**Does your claim involve content on GitHub or npm.js?**
14+
15+
GitHub
16+
17+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
18+
19+
I am the [private]
20+
21+
**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.**
22+
23+
Not online. Source code only given to paying customers. You can see our copyright notice at the top of every file that is posted on your site.
24+
25+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
26+
27+
ALL
28+
https://github.com/agninde/Driver_Example_CCS
29+
https://github.com/ilikerome/Driver_Example_CCS
30+
31+
**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.**
32+
33+
No
34+
35+
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> 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.**
36+
37+
Yes
38+
39+
**Is the work licensed under an open source license?**
40+
41+
No
42+
43+
**What would be the best solution for the alleged infringement?**
44+
45+
Reported content must be removed
46+
47+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
48+
49+
No
50+
51+
**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.**
52+
53+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
54+
55+
**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.**
56+
57+
**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>.**
58+
59+
**So that we can get back to you, please provide either your telephone number or physical address.**
60+
61+
[private]
62+
63+
CCS Inc.
64+
[private]
65+
[private]
66+
67+
**Please type your full legal name below to sign this request.**
68+
69+
[private]

0 commit comments

Comments
 (0)