Autofix: Add community files

[atomist:generated] [atomist:autofix=add_community_files]

CODE_OF_CONDUCT.md

@@ -10,22 +10,22 @@ race, religion, or sexual identity and orientation.
 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
+-   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
+-   The use of sexualized language or imagery and unwelcome sexual
     attention or advances
-*   Trolling, insulting/derogatory comments, and personal or political
+-   Trolling, insulting/derogatory comments, and personal or political
     attacks
-*   Public or private harassment
-*   Publishing others' private information, such as a physical or
+-   Public or private harassment
+-   Publishing others' private information, such as a physical or
     electronic address, without explicit permission
-*   Other conduct which could reasonably be considered inappropriate
+-   Other conduct which could reasonably be considered inappropriate
     in a professional setting
 
 Project maintainers are responsible for clarifying the standards of
@@ -53,7 +53,7 @@ at [code-of-conduct@atomist.com][email]. All complaints will be
 reviewed and investigated and will result in a response that is deemed
 necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of
-an incident.  Further details of specific enforcement policies may be
+an incident. Further details of specific enforcement policies may be
 posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct

CONTRIBUTING.md

@@ -1,18 +1,18 @@
 # Contributing to Atomist open source projects
 
-Have something you would like to contribute to this project?  Awesome,
-and thanks for taking time to contribute!  Here's what you need to
+Have something you would like to contribute to this project? Awesome,
+and thanks for taking time to contribute! Here's what you need to
 know.
 
 ## Contributing code
 
 Is there an improvement to existing functionality or an entirely new
-feature you would like to see?  Before creating enhancement
+feature you would like to see? Before creating enhancement
 suggestions, please check the issue list as you might find out that
 you don't need to create one.
 
-Did you know we have a [Slack community][slack]?  This might be a
-great place to talk through your idea before starting.  It allows you
+Did you know we have a [Slack community][slack]? This might be a
+great place to talk through your idea before starting. It allows you
 to see if anyone else is already working on something similar, having
 the same issue or to get feedback on your enhancement idea.
 Discussing things with the community first is likely to make the
@@ -25,21 +25,21 @@ If you do not find an open issue related to your contribution and
 discussions in the Slack community are positive, the next thing to do
 is to create an issue in the appropriate GitHub repository.
 
-*   Before we can accept any code changes into the Atomist codebase,
-    we need to get some of the legal stuff covered.  This is pretty
-    standard for open-source projects.  We are using
+-   Before we can accept any code changes into the Atomist codebase,
+    we need to get some of the legal stuff covered. This is pretty
+    standard for open-source projects. We are using
     [cla-assisant.io][cla-assistant] to track our Contributor License
-    Agreement (CLA) signatures.  If you have not signed a CLA for the
+    Agreement (CLA) signatures. If you have not signed a CLA for the
     repository to which you are contributing, you will be prompted to
     when you create a pull request (PR).
-*   Be sure there is an open issue related to the contribution.
-*   Code contributions should successfully build and pass tests.
-*   Commit messages should follow the [standard format][commit] and
+-   Be sure there is an open issue related to the contribution.
+-   Code contributions should successfully build and pass tests.
+-   Commit messages should follow the [standard format][commit] and
     should include a [reference][ref] to the open issue they are
     addressing.
-*   All code contributions should be submitted via
+-   All code contributions should be submitted via
     a [pull request (PR) from a forked GitHub repository][pr].
-*   Your PR will be reviewed by an Atomist developer.
+-   Your PR will be reviewed by an Atomist developer.
 
 [cla-assistant]: https://cla-assistant.io/
 [commit]: http://chris.beams.io/posts/git-commit/
@@ -52,32 +52,32 @@ Please go through the checklist below before reporting a
 problem. There's a chance it may have already been reported, or
 resolved.
 
-*   Check if you can reproduce the problem in the latest version of
+-   Check if you can reproduce the problem in the latest version of
     the project.
-*   Search the [atomist-community Slack][slack] community for common
+-   Search the [atomist-community Slack][slack] community for common
     questions and problems.
-*   Understand which repo the bug should be reported in.
-*   Scan the list of issues to see if the problem has previously been
-    reported.  If so, you may add a comment to the existing issue
+-   Understand which repo the bug should be reported in.
+-   Scan the list of issues to see if the problem has previously been
+    reported. If so, you may add a comment to the existing issue
     rather than creating a new one.
 
 You went through the list above and it is still something you would
-like to report?  Then, please provide us with as much of the context,
+like to report? Then, please provide us with as much of the context,
 by explaininig the problem and including any additional details that
-would help maintainers reproduce the problem.  The more details you
+would help maintainers reproduce the problem. The more details you
 provide in the bug report, the better.
 
-Bugs are tracked as GitHub issues.  After you've determined which
+Bugs are tracked as GitHub issues. After you've determined which
 repository your bug is related to, create an issue on that repository
-and provide as much information as possible.  Feel free to use
+and provide as much information as possible. Feel free to use
 the bug report template below if you like.
 
 At a minimum include the following:
 
-*   Where did you find the bug? For example, did you encounter the bug
+-   Where did you find the bug? For example, did you encounter the bug
     in chat, the CLI, somewhere else?
-*   What version are you using?
-*   What command were you using when it happened? (including
+-   What version are you using?
+-   What command were you using when it happened? (including
     parameters where applicable)
 
 ```
@@ -106,8 +106,8 @@ At a minimum include the following:
 ```
 
 This project adheres to the Contributor Covenant [code of
-conduct][conduct].  By participating, you are expected to uphold this
-code.  Please report unacceptable behavior to
+conduct][conduct]. By participating, you are expected to uphold this
+code. Please report unacceptable behavior to
 [code-of-conduct@atomist.com][email].
 
 [conduct]: CODE_OF_CONDUCT.md

SECURITY.md

@@ -3,27 +3,27 @@
 This document outlines security procedures and general policies for the
 Atomist Open Source projects as found on https://github.com/atomist.
 
-  * [Reporting a Vulnerability](#reporting-a-vulnerability)
-  * [Disclosure Policy](#disclosure-policy)
+-   [Reporting a Vulnerability](#reporting-a-vulnerability)
+-   [Disclosure Policy](#disclosure-policy)
 
-## Reporting a Vulnerability 
+## Reporting a Vulnerability
 
 The Atomist OSS team and community take all security vulnerabilities
-seriously. Thank you for improving the security of our open source 
+seriously. Thank you for improving the security of our open source
 software. We appreciate your efforts and responsible disclosure and will
 make every effort to acknowledge your contributions.
 
 Report security vulnerabilities by emailing the Atomist security team at:
-    
-    security@atomist.com
+
+ security@atomist.com
 
 The lead maintainer will acknowledge your email within 24 hours, and will
-send a more detailed response within 48 hours indicating the next steps in 
+send a more detailed response within 48 hours indicating the next steps in
 handling your report. After the initial reply to your report, the security
 team will endeavor to keep you informed of the progress towards a fix and
 full announcement, and may ask for additional information or guidance.
 
-Report security vulnerabilities in third-party modules to the person or 
+Report security vulnerabilities in third-party modules to the person or
 team maintaining the module.
 
 ## Disclosure Policy
@@ -32,7 +32,7 @@ When the security team receives a security bug report, they will assign it
 to a primary handler. This person will coordinate the fix and release
 process, involving the following steps:
 
-  * Confirm the problem and determine the affected versions.
-  * Audit code to find any potential similar problems.
-  * Prepare fixes for all releases still under maintenance. These fixes
+-   Confirm the problem and determine the affected versions.
+-   Audit code to find any potential similar problems.
+-   Prepare fixes for all releases still under maintenance. These fixes
     will be released as fast as possible to NPM.