Skip to content

Commit 858dd43

Browse files
committed
another slight shuffling
1 parent 0bdb714 commit 858dd43

File tree

3 files changed

+20
-6
lines changed

3 files changed

+20
-6
lines changed

.github/pull_request_template.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
11
If you are looking to file or dispute a takedown notice by posting to this repository, please STOP :stop_sign: because we do not accept Pull Requests or other contributions to this repository.
22

3+
Read on to learn about the available paths forward.
4+
35
Please note that re-posting the exact same content that was the subject of a takedown notice without following the proper process ([outlined below](#responding-to-a-dmca-notice)) is a violation of GitHub’s [DMCA Policy](https://docs.github.com/en/github/site-policy/dmca-takedown-policy) and [Terms of Service](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies). If you commit or post content to this repository that violates our Terms of Service, we will delete that content and may suspend access to your account as well.
46

5-
Otherwise, read on to learn about the available paths forward.
67

78
#### Submitting a DMCA Notice
89

910
If you are a copyright owner wishing to submit a takedown notice, read our [DMCA Policy](https://docs.github.com/en/free-pro-team@latest/github/site-policy/dmca-takedown-policy) and [Guide to Submitting a DMCA Takedown Notice](https://docs.github.com/en/free-pro-team@latest/github/site-policy/guide-to-submitting-a-dmca-takedown-notice). You can submit the actual notice using our special [Copyright Claims Contact Form](https://github.com/contact/dmca).
1011

12+
1113
#### Responding to a DMCA Notice
1214

1315
If you are the owner of a repository that has been taken down, you have two main options:

CONTRIBUTING.md

+6-2
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,19 @@
11
This repository exists to provide transparency by posting the text of DMCA notices and counter notices received.
22

3-
If you are looking to file or dispute a takedown notice by posting to this repository, please STOP :stop_sign: because we do not accept Pull Requests or other contributions to this repository. If you would just like to comment on a commit to discuss it, that's fine, but again please note that GitHub does not actively monitor comments or other contributions to this repository. So if you want send a comment *to GitHub* for any reason about this repository, please [contact us directly](https://support.github.com/contact).
3+
If you are looking to file or dispute a takedown notice by posting to this repository, please STOP :stop_sign: because we do not accept Pull Requests or other contributions to this repository.
4+
5+
Read on to learn about the available paths forward.
6+
7+
If you would just like to comment on a commit to discuss it, that's fine, but again please note that GitHub does not actively monitor comments or other contributions to this repository. So if you want send a comment *to GitHub* for any reason about this repository, please [contact us directly](https://support.github.com/contact).
48

59
Please note that re-posting the exact same content that was the subject of a takedown notice without following the proper process ([outlined below](#responding-to-a-dmca-notice)) is a violation of GitHub’s [DMCA Policy](https://docs.github.com/en/github/site-policy/dmca-takedown-policy) and [Terms of Service](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies). If you commit or post content to this repository that violates our Terms of Service, we will delete that content and may suspend access to your account as well.
610

7-
Otherwise, read on to learn about the available paths forward.
811

912
#### Submitting a DMCA Notice
1013

1114
If you are a copyright owner wishing to submit a takedown notice, read our [DMCA Policy](https://docs.github.com/en/free-pro-team@latest/github/site-policy/dmca-takedown-policy) and [Guide to Submitting a DMCA Takedown Notice](https://docs.github.com/en/free-pro-team@latest/github/site-policy/guide-to-submitting-a-dmca-takedown-notice). You can submit the actual notice using our special [Copyright Claims Contact Form](https://github.com/contact/dmca).
1215

16+
1317
#### Responding to a DMCA Notice
1418

1519
If you are the owner of a repository that has been taken down, you have two main options:

README.md

+11-3
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,36 @@
11
#### What is this?
2+
23
Inspired by [Lumen](https://lumendatabase.org/topics/1) (*formerly Chilling Effects*) and [Google](https://cloud.google.com/storage/docs/dmca), this repo contains the text of DMCA takedown notices and counter-notices we've received here at GitHub. We publish them as they are received, with only personally identifiable information redacted.
34

5+
46
#### Why is this?
7+
58
In short, we believe that transparency on a specific and ongoing level is essential to good governance. Chilling Effects/Lumen explained it well in 2014 ([archive.org mirror; not present on their current site](https://web.archive.org/web/20140101160724/http://chillingeffects.org/#donato-if:~:text=We%20are%20excited%20about%20the%20new,its%20misuse%20to%20%22chill%22%20legitimate%20activity.)): "We are excited about the new opportunities the Internet offers individuals to express their views . . . but concerned that not everyone feels the same way. Study to date suggests that cease and desist letters often silence Internet users, whether or not their claims have legal merit." (About, ChillingEffects.org, Sept. 2014, licensed under [CC-BY-3.0](http://creativecommons.org/licenses/by/3.0/us/)). Similarly, we post takedown notices here to document their potential to "chill" speech.
69

10+
711
#### What does it mean if there's a notice posted here?
12+
813
It only means that we received the notice on the indicated date. It does ***not*** mean that the content was unlawful or wrong. It does ***not*** mean that the user identified in the notice has done anything wrong. We don't make or imply any judgment about the merit of the claims they make. We post these notices and requests only for informational purposes.
914

1015
For more details, see our [DMCA policy](https://help.github.com/articles/dmca-takedown-policy/).
1116

17+
1218
#### Contributing
1319

14-
We do not accept Pull Requests in this repository.
20+
If you are looking to file or dispute a takedown notice by posting to this repository, please STOP :stop_sign: because we do not accept Pull Requests or other contributions to this repository.
1521

16-
If you are looking to file or dispute a takedown notice by posting to this repository, please STOP :stop_sign: because we do not accept Pull Requests or other contributions to this repository. If you would just like to comment on a commit to discuss it, that's fine, but again please note that GitHub does not actively monitor comments or other contributions to this repository. So if you want send a comment *to GitHub* for any reason about this repository, please [contact us directly](https://support.github.com/contact).
22+
Read on to learn about the available paths forward.
23+
24+
If you would just like to comment on a commit to discuss it, that's fine, but again please note that GitHub does not actively monitor comments or other contributions to this repository. So if you want send a comment *to GitHub* for any reason about this repository, please [contact us directly](https://support.github.com/contact).
1725

1826
Please note that re-posting the exact same content that was the subject of a takedown notice without following the proper process ([outlined below](#responding-to-a-dmca-notice)) is a violation of GitHub’s [DMCA Policy](https://docs.github.com/en/github/site-policy/dmca-takedown-policy) and [Terms of Service](https://docs.github.com/en/github/site-policy/github-acceptable-use-policies). If you commit or post content to this repository that violates our Terms of Service, we will delete that content and may suspend access to your account as well.
1927

20-
Otherwise, read on to learn about the available paths forward.
2128

2229
#### Submitting a DMCA Notice
2330

2431
If you are a copyright owner wishing to submit a takedown notice, read our [DMCA Policy](https://docs.github.com/en/free-pro-team@latest/github/site-policy/dmca-takedown-policy) and [Guide to Submitting a DMCA Takedown Notice](https://docs.github.com/en/free-pro-team@latest/github/site-policy/guide-to-submitting-a-dmca-takedown-notice). You can submit the actual notice using our special [Copyright Claims Contact Form](https://github.com/contact/dmca).
2532

33+
2634
#### Responding to a DMCA Notice
2735

2836
If you are the owner of a repository that has been taken down, you have two main options:

0 commit comments

Comments
 (0)