Add COC, contribution docs, and maintainerd configuration.

Author: divmain

.maintainerd

@@ -0,0 +1,47 @@
+log: true
+pullRequest:
+  preamble: >
+    The maintainers of this repo require that all pull request submitters adhere to the following:
+  items:
+    - prompt: >
+        I have read and will comply with the
+        [contribution guidelines](https://github.com/FormidableLabs/rapscallion/blob/master/CONTRIBUTE.md).
+      default: false
+      required: true
+    - prompt: >
+        I have read and will comply with the
+        [code of conduct](https://github.com/FormidableLabs/rapscallion/blob/master/CONTRIBUTE.md).
+      default: false
+      required: true
+    - prompt: All related documentation has been updated to reflect the changes made.
+      default: false
+      required: true
+    - prompt: My commit messages are cleaned up and ready to merge.
+      default: false
+      required: true
+  semver:
+    enabled: true
+commit:
+  subject:
+    mustHaveLengthBetween: [8, 100]
+    mustMatch: !!js/regexp /^(Fix|Enhancement|Feature|Docs|Other):\s.*/
+    mustNotMatch: !!js/regexp /^fixup!/
+  message:
+    enforceEmptySecondLine: true
+    linesMustHaveLengthBetween: [0, 100]
+issue:
+  onLabelAdded:
+    not-enough-information:
+      action: comment
+      data: |
+        This issue has been tagged with the `not-enough-information` label.  In order for us to help you,
+        please respond with the following information:
+
+        - A description of the problem, including any relevant error output that can find.
+        - A full repro, if possible.  Otherwise, steps to reproduce.
+        - The versions of the packages that you are using.
+        - The operating system that you are using.
+        - The browser or environment where the issue occurs.
+
+        If we receive no response to this issue within 2 weeks, the issue will be closed.  If that happens,
+        feel free to re-open with the requested information.  Thank you!

COC.md

@@ -0,0 +1,75 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Aggresive and/or demanding language
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the author at <[email protected]>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The maintainers are
+obligated to protect confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTE.md

@@ -0,0 +1,59 @@
+# Contribute
+
+If you're interested in adding features, reporting/fixing bugs, or just discussing the future of rapscallion, this is the place to start.  Please feel free to reach out if you have questions or comments by opening an [issue](https://github.com/FormidableLabs/rapscallion/issues).
+
+
+## Adding new features
+
+If there's a feature you'd like to see that isn't already in-progress or documented, there are two ways you can go about it:
+
+- open an issue for discussion; or
+- fork and submit a PR.
+
+Either way is fine, so long as you remember your PR may not be accepted as-is or at all.  If a feature request is reasonable, though, it'll most likely be included one way or another.
+
+Some other things to remember:
+
+- Please respect the project layout and hierarchy, to keep things organized.
+- All code is linted.  Outside of that, please try to conform to the code style and idioms that are used throughout the project.
+- Include descriptions for issues and PRs.
+- Please comply with the project's [code of conduct](./COC.md).
+
+I'm busy and travel sometimes for work - so if I don't respond immediately, please be patient.  I promise to reply!
+
+## Commit message structure
+
+Please follow the following commit message structure when submitting your pull request:
+
+    TYPE: Short commit message
+
+    Detailed
+    commit
+    info
+
+For the value of **`TYPE`**, please use one of **`Feature`**, **`Enhancement`**, or **`Fix`**.
+
+This is required in order to help us automate tasks such as changelog generation.
+
+
+# Bugs
+
+If you encounter a bug, please check for an open issue that already captures the problem you've run into.  If it doesn't exist yet, create it!
+
+Please include as much information as possible, including:
+
+- A full repro, if possible.
+- The versions of the packages that you're using.
+- The browser or environment where the issue occurs.
+- Any error messages or debug output that seems relevant.
+
+If you're interested in tackling a bug, please say so.
+
+
+# Documentation
+
+If you make changes, please remember to update the documentation to reflect the new behavior.
+
+# Publishing
+
+All changes are published automatically whenever a pull request is merged.  As part of the PR process, you will be asked to provide the information necessary to make that happen.