Skip to content

Commit 9543c7e

Browse files
Merge pull request #20236 from github/updates
Added 2026/04/2026-04-09-devarch-counternotice.md
2 parents 72ec446 + 0b7a940 commit 9543c7e

1 file changed

Lines changed: 42 additions & 0 deletions

File tree

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
**Are you the owner of the content that has been disabled, or authorized to act on the owner’s behalf?**
2+
3+
Yes, I am the content owner.
4+
5+
**Please describe the nature of your content ownership or authorization to act on the owner's behalf.**
6+
7+
I am the [private] of the disabled GitHub repository https://github.com/SangeetAgarwal/specarc, and I am submitting this counter notice on [private] [private] behalf.
8+
9+
**What files were taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
10+
11+
The entire repository was disabled:
12+
13+
https://github.com/SangeetAgarwal/specarc
14+
15+
**Do you want to make changes to your repository or do you want to dispute the notice?**
16+
17+
Dispute the notice.
18+
19+
**Is there anything else you think we should know about why you believe the material was removed as a result of a mistake?**
20+
21+
[private] forked the claimant’s GitHub repository, [private], while it was publicly accessible and published under the MIT License. [private] also submitted a pull request to that same repository, and the claimant reviewed and merged it. After that, the claimant changed the repository’s visibility and made it private. After the fork, [private] continued to develop my repository through additional commits containing my own subsequent work.
22+
23+
[private] was sent an invitation to the private repository [private], but [private] did not accept that invitation and [private] did not access that private repository. At no time have [private] had access to any private repositories owned by the claimant. [private] did not bypass any password, encryption, access control, or other technological protection measure. [private] repository was based on the publicly accessible GitHub repository [private], not on a private repository.
24+
25+
The presence of the claimant’s name in the LICENSE file is not evidence of infringement. It reflects retention of the original copyright and permission notice as required by the MIT License.
26+
27+
For the reasons stated above, I have a good-faith belief that [private] repository was removed or disabled as a result of mistake or misidentification.
28+
29+
**I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled.**
30+
31+
**I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person.**
32+
33+
**Please confirm that you have you have read our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-counter-notice">Guide to Submitting a DMCA Counter Notice</a>.**
34+
35+
**So that the complaining party can get back to you, please provide both your telephone number and physical address.**
36+
37+
Telephone Number: [private]
38+
Physical Address: [private]
39+
40+
**Please type your full legal name below to sign this request.**
41+
42+
[private]

0 commit comments

Comments
 (0)