Initial import of Open XDMoD 6.5

Author: xdmod

.editorconfig

@@ -0,0 +1,23 @@
+# EditorConfig is awesome: http://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+# Indentation override for all JS under lib directory
+[package.json]
+indent_size = 2
+
+[*.{remarkrc,eslintrc}]
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false

.eslintrc.json

@@ -0,0 +1,66 @@
+{
+  "env": {},
+  "globals": {},
+  "extends": "eslint:recommended",
+  "rules": {
+    "curly": 2,
+    "guard-for-in": 2,
+    "no-extend-native": 2,
+    "block-scoped-var": 1,
+    "no-use-before-define": 2,
+    "no-caller": 2,
+    "no-sequences": 2,
+    "no-new": 2,
+    "no-extra-parens": 1,
+    "dot-notation": [
+      1,
+      {
+        "allowPattern": "^[a-z]+(_[a-z]+)+$"
+      }
+    ],
+    "no-implicit-coercion": [
+      2,
+      {
+        "boolean": true,
+        "number": true,
+        "string": false
+      }
+    ],
+    "no-multi-spaces": 2,
+    "key-spacing": [
+      2,
+      {
+        "beforeColon": false,
+        "afterColon": true
+      }
+    ],
+    "comma-spacing": [
+      2,
+      {
+        "before": false,
+        "after": true
+      }
+    ],
+    "semi-spacing": [
+      2,
+      {
+        "before": false,
+        "after": true
+      }
+    ],
+    "no-spaced-func": 2,
+    "no-trailing-spaces": 2,
+    "eol-last": 2,
+    "semi": 2,
+    "space-infix-ops": 2,
+    "consistent-this": [
+      1,
+      "self"
+    ],
+    "linebreak-style": [
+      2,
+      "unix"
+    ],
+    "keyword-spacing": 1
+  }
+}

.github/CONTRIBUTING.md

@@ -0,0 +1,51 @@
+# How to Contribute
+
+Third-party patches are essential for keeping XDMoD great. There are a
+few guidelines that we need contributors to follow so that we can have a
+chance of keeping on top of things.
+
+## Getting Started
+
+* Contact us about the feature or bug fix you intend to work on before you start.
+  * The change may be something we are already working on internally, or we
+    may have advice on how best to proceed.
+  * If working on a bug fix, include:
+    * Steps to reproduce the bug
+    * The earliest version that you know has the bug
+  * We can be **publicly** reached via:
+    * The issues tab of this repository
+    * The XDMoD mailing list (see [the Open XDMoD support page][support])
+  * We can be **privately** reached via:
+    * The XDMoD support email address (see [the Open XDMoD support page][support])
+* Once you have the go-ahead, fork the repository on GitHub and make the
+  changes there.
+
+## Making Changes
+
+* Create a topic branch from where you want to base your work.
+  * Base your work on the oldest version of XDMoD you want to change. If you
+    want to fix a bug in XDMoD 6.5 and newer, you would create a topic branch
+    on `xdmod6.5` (`git checkout -b fix/my_contribution xdmod6.5`).
+* Make commits of logical units. ([Squash](https://www.youtube.com/watch?v=qh9KtjfjzCU)
+  your commits before submission if necessary.)
+* Check for unnecessary whitespace with `git diff --check` before committing.
+
+## Style Guidelines (linting)
+
+* If there exists a linter config file for some aspect of the project (e.g. `.eslintrc.json`, `.editorconfig`, `.remarkrc`), please use the associated linter with the config.
+* If there is no applicable linter or linter config when editing a file, try to stick with its current style.
+* Make sure that you fix any errors found by all configured linters (e.g. remark-lint, ESLint, phpcs).
+* If an error or warning can't be fixed, please add comments to the pull/commit explaining why.
+* We realize that all code, including existing code, might not pass the linters (as configured).
+    * If you want to fix stylistic errors for an entire file that you're working on (which is appreciated!), fix it in a separate commit before starting on any functional code changes. This makes it easier to see the functional changes.
+    * Please do not submit changes that are _purely_ style fixes. While we would love to see the code get tidied up, every change introduced increases the chance of conflicts for someone else's work in progress.
+
+## Submitting Changes
+
+* Make sure you have followed the style guidelines.
+* Push your changes to a topic branch in your fork of the repository.
+* All relevant documentation should be added to or updated as part of your pull request.
+* Submit a pull request to the repository.
+* After feedback has been given, we expect responses (comments and/or commits) within two weeks. After two weeks of inactivity, we may close the pull request.
+
+[support]: http://open.xdmod.org/support.html

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,32 @@
+<!--- Provide a general summary of the issue in the Title above -->
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+* Environment name and version (e.g. Chrome 39, Node.js 5.4):
+* Operating system and version (desktop or mobile):
+* Link to your project:

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,29 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+<!--- Describe your changes in detail -->
+<!--- Include screenshots for GUI changes if appropriate -->
+<!--- If any documentation outside of this repo needs to be added or updated,
+      please include links to the relevant docs and how they should be changed -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## Tests performed
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Types of changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My code follows the code style of this project as found in the **CONTRIBUTING** document.
+- [ ] I have added tests to cover my changes.
+- [ ] All new and existing tests passed.