Update 2022-06-24-headspace.md

.github/.gitignore

@@ -0,0 +1 @@
+node_modules/

.github/pull_request_template.md

@@ -0,0 +1,21 @@
+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.
+
+Read on to learn about the available paths forward.
+
+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.
+
+
+#### Submitting a DMCA Notice
+
+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).
+
+
+#### Responding to a DMCA Notice
+
+If you are the owner of a repository that has been taken down, you have two main options:
+
+  - Do you want to [make changes](https://docs.github.com/en/free-pro-team@latest/github/site-policy/dmca-takedown-policy#c-what-if-i-inadvertently-missed-the-window-to-make-changes) to the repository that would remove the allegedly infringing content? If that is possible in your case, [contact us](https://support.github.com/contact) to let us know that you would like to make the changes.
+
+  - Do you want to formally dispute the action by [submitting a counter notice](https://docs.github.com/en/free-pro-team@latest/github/site-policy/guide-to-submitting-a-dmca-counter-notice)? Maybe the person sending the takedown notice does not hold the copyright or did not realize that you have a license or made some other mistake in their takedown notice. If you believe your content on GitHub was mistakenly disabled by a DMCA takedown request, you have the right to contest the takedown by [submitting a counter notice](https://docs.github.com/en/free-pro-team@latest/github/site-policy/guide-to-submitting-a-dmca-counter-notice). If you do, we will wait 10-14 days and then re-enable your content unless the copyright owner initiates a legal action before then.
+
+If you do not want to make changes or dispute the notice, but still have general concerns about the copyright laws and how they apply in your case, know that GitHub and developers have the opportunity and a voice to advocate for changes in law and public policy to better support software development. We are constantly looking to [advocate for developers](https://github.blog/category/company/policy/), so feel free to [reach out](https://support.github.com/contact) and let us know your concerns. We also encourage you to [learn more about copyright and speak up](https://docs.github.com/en/free-pro-team@latest/github/site-policy/dmca-takedown-policy#learn-more-and-speak-up) by reaching out to the Copyright Office or your local lawmakers to voice your concerns.

.github/script/validate-filepaths/index.js

@@ -0,0 +1,103 @@
+import walkSync from "walk-sync";
+import {
+  isFileInCorrectFolder,
+  isFilepathDateValid,
+  getNoticeCategory,
+} from "./utils/validators.js";
+import _ from "lodash";
+const { partition } = _;
+import { setOutput } from "@actions/core";
+
+const { CHANGED_FILES } = process.env;
+const dmcaFilesChangedInPr = CHANGED_FILES.split("\n").filter(
+  isFileInsideAYearFolder
+);
+
+const [prChangedFilesWithValidDates, prChangedFilesWithInvalidDates] =
+  partition(dmcaFilesChangedInPr, isFilepathDateValid);
+const [prChangedFilesinCorrectFolder, prChangedFilesNotInCorrectFolder] =
+  partition(prChangedFilesWithValidDates, isFileInCorrectFolder);
+
+let commentBody = `Thanks for the PR!
+# Files changed in this PR
+`;
+let commentCopyForFilesChangedInThisPr =
+  prChangedFilesWithInvalidDates.length ||
+  prChangedFilesNotInCorrectFolder.length
+    ? ` I've scanned the changed files and found some issues to double check:`
+    : ` All DMCA notices changed in this PR appear to have valid YYYY-MM-DD dates and seem to be in the correct folder.`;
+
+commentCopyForFilesChangedInThisPr += prChangedFilesWithInvalidDates.length
+  ? `\n\n**Notices that don't contain a date that conforms to the YYYY-MM-DD format:**\n\n${prChangedFilesWithInvalidDates
+      .map((file) => `- ${file}`)
+      .join("\n")}`
+  : "";
+
+commentCopyForFilesChangedInThisPr += prChangedFilesNotInCorrectFolder.length
+  ? `\n\n**Notices that might need to be moved to the correct year/month folder:**\n\n${prChangedFilesNotInCorrectFolder
+      .map((file) => `- ${file}`)
+      .join("\n")}`
+  : "";
+
+let commentCopyForCategoriesOfFilesChangedInThisPr = `\n\n**Notices appear to fall into the following categories:**
+| Filepath | Category |
+| --- | --- |
+${dmcaFilesChangedInPr
+  .map((filepath) => {
+    const noticeCategory = getNoticeCategory(filepath);
+    return "| " + filepath + " | " + noticeCategory + " |";
+  })
+  .join("\n")}
+`;
+
+commentBody += commentCopyForFilesChangedInThisPr;
+commentBody += commentCopyForCategoriesOfFilesChangedInThisPr;
+
+const filesInDmcaNoticeFolders = walkSync(".", { directories: false })
+  .filter(isFileInsideAYearFolder)
+  .filter((file) => {
+    const isFileAmongChangedFiles = dmcaFilesChangedInPr.includes(file);
+    return !isFileAmongChangedFiles; // filter out files that are in the changed files list
+  });
+
+const [filesWithValidDates, filesWithInvalidDates] = partition(
+  filesInDmcaNoticeFolders,
+  isFilepathDateValid
+);
+const [filesInCorrectFolder, filesNotInCorrectFolder] = partition(
+  filesWithValidDates,
+  isFileInCorrectFolder
+);
+
+let commentCopyForAllDmcaNoticesInRepo =
+  filesWithInvalidDates.length || filesNotInCorrectFolder.length
+    ? `\n# Other Files in Repo\nI've also scanned the rest of the repo and found some files to double check:`
+    : `\n# Other Files in Repo\nThe other DMCA notices in the repo appear to have valid YYYY-MM-DD dates and seem to be in the correct folder.`;
+
+const invalidDatesList = filesWithInvalidDates.length
+  ? `\n\n**Notices that don't contain a date that conforms to the YYYY-MM-DD format:**\n\n${filesWithInvalidDates
+      .map((file) => `- ${file}`)
+      .join("\n")}`
+  : "";
+
+const incorrectFolderList = filesNotInCorrectFolder.length
+  ? `\n\n**Notices that might need to be moved to the correct year/month folder:**\n\n${filesNotInCorrectFolder
+      .map((file) => `- ${file}`)
+      .join("\n")}`
+  : "";
+
+commentCopyForAllDmcaNoticesInRepo += invalidDatesList;
+commentCopyForAllDmcaNoticesInRepo += incorrectFolderList;
+
+commentBody += commentCopyForAllDmcaNoticesInRepo;
+
+setOutput("COMMENT_BODY", commentBody);
+
+/**
+ * Returns true if the file is in a folder at the root directory of the repo of the form YYYY
+ * @param {string} filepath
+ * @returns {boolean}
+ */
+function isFileInsideAYearFolder(filepath) {
+  return filepath.match(/^\d{4}/) !== null;
+}