add CODE_OF_CONDUCT (codesandbox#1223)

Author: SaraVieira

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# CodeSandbox 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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
+- 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 project team at [INSERT EMAIL ADDRESS]. 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 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -2,10 +2,15 @@
 
 ## Table of Contents
 
-* [Code Organization](#code-organization)
-* [Setting Up the project locally](#setting-up-the-project-locally)
-* [Submitting a Pull Request](#submitting-a-pull-request)
-* [Add yourself as a contributor](#add-yourself-as-a-contributor)
+- [Code of Conduct](#code-of-conduct)
+- [Code Organization](#code-organization)
+- [Setting Up the project locally](#setting-up-the-project-locally)
+- [Submitting a Pull Request](#submitting-a-pull-request)
+- [Add yourself as a contributor](#add-yourself-as-a-contributor)
+
+## Code of Conduct
+
+We have a code of conduct you can find [here](https://github.com/CompuIves/codesandbox-client/blob/master/CODE_OF_CONDUCT.md) and every contributor is expect to obey the rules on it. Any issues or PR may be closes if not in terms with it.
 
 ## Code Organization
 
@@ -19,26 +24,27 @@ The CodeSandbox client is currently divided in to 5 parts. We use `lerna` to sha
 
 This version of CodeSandbox is using the production server as source of truth, this is specified by the environment variable `LOCAL_SERVER`. If you're working on a feature that needs you to be logged in, you can login on [https://codesandbox.io/](https://codesandbox.io/) and copy the contents of the `jwt` local storage key over to your development environment on [http://localhost:3000/](http://localhost:3000/). **Be very careful with how you handle the token**, as anyone who knows it can login as you and have read/write access to all your CodeSandbox content!
 
-**Working on your first Pull Request?** You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github)
+**Working on your first Pull Request?** You can learn how from this _free_ series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github)
 
 ## Setting Up the project locally
 
 To install the project you need to have `yarn` and `node`
 
-1. [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork:
+1.  [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork:
+
+    ```
+    # Clone your fork
+    git clone https://github.com/<your-username>/codesandbox-client.git
 
-   ```
-   # Clone your fork
-   git clone https://github.com/<your-username>/codesandbox-client.git
+    # Navigate to the newly cloned directory
+    cd codesandbox-client
+    ```
 
-   # Navigate to the newly cloned directory
-   cd codesandbox-client
-   ```
-2. `yarn` to install dependencies
-3. `yarn start` to start the app
-   * this builds the dependencies (`codesandbox-api` and `codesandbox-browserfs`) and runs the `app` development environment, available on [http://localhost:3000/s/new](http://localhost:3000/s/new)
-   * on subsequent runs you can also bypass dependencies building and use `yarn start:fast`
-   * if you want to work on the homepage, start it with `yarn start:home`, it will be available on [http://localhost:8000/](http://localhost:8000/)
+2.  `yarn` to install dependencies
+3.  `yarn start` to start the app
+    - this builds the dependencies (`codesandbox-api` and `codesandbox-browserfs`) and runs the `app` development environment, available on [http://localhost:3000/s/new](http://localhost:3000/s/new)
+    - on subsequent runs you can also bypass dependencies building and use `yarn start:fast`
+    - if you want to work on the homepage, start it with `yarn start:home`, it will be available on [http://localhost:8000/](http://localhost:8000/)
 
 > Tip: Keep your `master` branch pointing at the original repository and make
 > pull requests from branches on your fork. To do this, run: