Skip to content

Commit 8101696

Browse files
Merge pull request #13129 from github/updates
Added 2023/03/2023-03-22-xatechnologies.md
2 parents 0b5ba0c + 1692329 commit 8101696

File tree

1 file changed

+74
-0
lines changed

1 file changed

+74
-0
lines changed
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
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+
No
8+
9+
**Does your claim involve content on GitHub or npm.js?**
10+
11+
GitHub
12+
13+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
14+
15+
The code is Intellectual Property of XATechnologies, and is a company that I am [private].
16+
17+
The developer that is infringing the copyright was employed at our firm and has copied several repositories and copied these without authorization.
18+
19+
**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.**
20+
21+
There are several repositories of code posted online.
22+
https://github.com/jbermudezlaya/crm
23+
https://github.com/jbermudezlaya/ata
24+
https://github.com/jbermudezlaya/das
25+
https://github.com/jbermudezlaya/gea
26+
https://github.com/jbermudezlaya/infra
27+
https://github.com/jbermudezlaya/aviony
28+
29+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
30+
31+
All repositories need to be taken down immediately
32+
33+
**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.**
34+
35+
No
36+
37+
**<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.**
38+
39+
https://github.com/jbermudezlaya/crm
40+
https://github.com/jbermudezlaya/ata
41+
https://github.com/jbermudezlaya/das
42+
https://github.com/jbermudezlaya/gea
43+
https://github.com/jbermudezlaya/infra
44+
https://github.com/jbermudezlaya/aviony
45+
46+
**Is the work licensed under an open source license?**
47+
48+
No
49+
50+
**What would be the best solution for the alleged infringement?**
51+
52+
Reported content must be removed
53+
54+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
55+
56+
[private]
57+
[private]
58+
59+
**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.**
60+
61+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
62+
63+
**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.**
64+
65+
**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>.**
66+
67+
**So that we can get back to you, please provide either your telephone number or physical address.**
68+
69+
Telephone number [private]
70+
Address [private]
71+
72+
**Please type your full legal name below to sign this request.**
73+
74+
[private]

0 commit comments

Comments
 (0)