.editorconfig

@@ -10,9 +10,3 @@ insert_final_newline = true
 trim_trailing_whitespace = true
 indent_style = space
 indent_size = 2
-
-[Makefile]
-indent_style = tab
-
-[*.md]
-trim_trailing_whitespace = false

.eleventy.js

@@ -0,0 +1,44 @@
+'use strict';
+
+module.exports = function(eleventyConfig) {
+  eleventyConfig.addPassthroughCopy('docs/css');
+  eleventyConfig.addPassthroughCopy('docs/js');
+  eleventyConfig.addPassthroughCopy('docs/images');
+  eleventyConfig.addPassthroughCopy('docs/CNAME');
+  eleventyConfig.addPassthroughCopy('docs/_headers');
+  eleventyConfig.addPassthroughCopy('docs/favicon.ico');
+
+  eleventyConfig.addPassthroughCopy('docs/example');
+
+  /* Markdown Plugins */
+  const markdown = require('markdown-it')({
+    html: true,
+    linkify: true
+  });
+
+  markdown.use(require('markdown-it-anchor'), {
+    slugify: require('uslug'),
+    permalink: true,
+    permalinkBefore: true,
+    permalinkClass: 'direct-link',
+    permalinkSymbol: '#'
+  });
+
+  markdown.use(require('markdown-it-attrs'), {
+    leftDelimiter: '{:',
+    rightDelimiter: '}'
+  });
+
+  markdown.use(require('markdown-it-prism'));
+
+  eleventyConfig.setLibrary('md', markdown);
+
+  return {
+    passthroughFileCopy: true,
+    dir: {
+      input: 'docs',
+      includes: '_includes',
+      output: 'docs/_site'
+    }
+  };
+};

.eslintignore

@@ -0,0 +1,8 @@
+coverage/
+mocha.js
+*.fixture.js
+docs/
+out/
+!lib/mocha.js
+test/integration/fixtures
+!.*.js

.eslintrc.yml

@@ -0,0 +1,90 @@
+root: true
+extends:
+  - semistandard
+  - plugin:prettier/recommended
+env:
+  node: yes
+  browser: yes
+parserOptions:
+  ecmaVersion: 5
+  ecmaFeatures:
+    globalReturn: no
+    jsx: no
+  sourceType: script
+rules:
+  strict:
+    - error
+    - safe
+overrides:
+  - files:
+      - scripts/**/*.js
+      - package-scripts.js
+      - karma.conf.js
+      - .wallaby.js
+      - .eleventy.js
+      - bin/*
+      - lib/cli/**/*.js
+      - test/node-unit/**/*.js
+      - test/integration/options/watch.spec.js
+      - test/integration/helpers.js
+      - lib/growl.js
+    parserOptions:
+      ecmaVersion: 6
+    env:
+      browser: no
+
+  - files:
+      - test/**/*.{js,mjs}
+    env:
+      mocha: yes
+    globals:
+      expect: no
+  - files:
+      - bin/*
+      - lib/**/*.js
+    rules:
+      no-restricted-globals:
+        - error
+        - name: setTimeout
+          message: &GH-237 See https://github.com/mochajs/mocha/issues/237
+        - name: clearTimeout
+          message: *GH-237
+        - name: setInterval
+          message: *GH-237
+        - name: clearInterval
+          message: *GH-237
+        - name: setImmediate
+          message: *GH-237
+        - name: clearImmediate
+          message: *GH-237
+        - name: Date
+          message: *GH-237
+      no-restricted-modules:
+        - error
+        - timers
+      no-restricted-syntax:
+        - error
+        # disallow `global.setTimeout()`, `global.setInterval()`, etc.
+        - selector: 'CallExpression[callee.object.name=global][callee.property.name=/(set|clear)(Timeout|Immediate|Interval)/]'
+          message: *GH-237
+        # disallow `new global.Date()`
+        - selector: 'NewExpression[callee.object.name=global][callee.property.name=Date]'
+          message: *GH-237
+        # disallow property access of `global.<timer>.*`
+        - selector: '*[object.object.name=global][object.property.name=/(Date|(set|clear)(Timeout|Immediate|Interval))/]:expression'
+          message: *GH-237
+
+  - files:
+      - test/**/*.mjs
+    parserOptions:
+      ecmaVersion: 6
+      sourceType: module
+
+  - files:
+      - lib/reporters/*.js
+    rules:
+      no-restricted-syntax:
+        - error
+        # disallow Reporters using `console.log()`
+        - selector: 'CallExpression[callee.object.name=console][callee.property.name=log]'
+          message: &GH-3604 See https://github.com/mochajs/mocha/issues/3604

.fossaignore

@@ -0,0 +1,2 @@
+CONTRIBUTING.md
+MAINTAINERS.md

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,94 @@
+# Mocha Code of Conduct
+
+## Be friendly and patient
+
+We understand that everyone has different levels of experience or knowledge in many diverse fields, be it technical or
+non-technical in nature. We also have areas of knowledge we are eager to expand; we want to be a community where people
+can not only contribute, but feel comfortable to ask questions as well and learn along the way. If someone says something
+wrong, or says something accidentally offensive, respond with patience and try to keep it polite and civil. Remember that
+we all were newbies at one point.
+
+## Be welcoming
+
+We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not
+limited to, members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class,
+educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief,
+religion, and mental and physical ability.
+
+## Be considerate
+
+Your work will be used by other people, and you in turn will depend on the work of others. Any decision you make will affect
+users and colleagues, and you should take those consequences into account when making decisions. Remember that we’re a world-wide
+community, so you might not be communicating in someone else’s primary language.
+
+## Be respectful
+
+Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all
+experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important
+to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the JS Foundation
+community should be respectful when dealing with other members as well as with people outside the JS Foundation community.
+
+## Be careful in the words that you choose
+
+We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put
+down other participants. Harassment and other exclusionary behavior aren’t acceptable. This includes, but is not limited to:
+
+- Violent threats or language directed against another person.
+- Discriminatory jokes and language.
+- Posting sexually explicit or violent material.
+- Posting (or threatening to post) other people’s personally identifying information (“doxing”).
+- Personal insults, especially those using racist or sexist terms.
+- Unwelcome sexual attention.
+- Advocating for, or encouraging, any of the above behavior.
+- Repeated harassment of others. In general, if someone asks you to stop, then stop.
+
+## When we disagree, try to understand why
+
+Disagreements, both social and technical, happen all the time and JS Foundation projects are no exception. It is important
+that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of the JS
+Foundation comes from its varied community, people from a wide range of backgrounds. Different people have different
+perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t
+forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues
+and learning from mistakes.
+
+Original text courtesy of the Speak Up! project and Django Project.
+
+## QUESTIONS?
+
+If you have questions, please see the FAQ. If that doesn’t answer your questions, feel free to email report@lists.openjsf.org.
+
+# OpenJS Foundation Code of Conduct
+
+The OpenJS Foundation and its member projects use the Contributor
+Covenant v1.4.1 as its Code of Conduct. Refer to the following
+for the full text:
+
+- [english](https://www.contributor-covenant.org/version/1/4/code-of-conduct)
+- [translations](https://www.contributor-covenant.org/translations)
+
+Refer to the section on reporting and escalation in this document for the specific emails that can be used to report and escalate issues.
+
+## Reporting
+
+### Project Spaces
+
+For reporting issues in spaces related to a member project please use the email provided by the project for reporting. Projects handle CoC issues related to the spaces that they maintain. Projects maintainers commit to:
+
+- maintain the confidentiality with regard to the reporter of an incident
+- to participate in the path for escalation as outlined in
+  the section on Escalation when required.
+
+### Foundation Spaces
+
+For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization, use the email `report@lists.openjsf.org`. The Cross Project Council (CPC) is responsible for managing these reports and commits to:
+
+- maintain the confidentiality with regard to the reporter of an incident
+- to participate in the path for escalation as outlined in
+  the section on Escalation when required.
+
+## Escalation
+
+The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. In order to escalate to the CoCP send an email to `"coc-escalation@lists.openjsf.org`.
+
+For more information, refer to the full
+[Code of Conduct governance document](https://github.com/openjs-foundation/bootstrap/blob/master/proposals/stage-1/CODE_OF_CONDUCT/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md).