add code of conduct and contributing documents

Author: pocketjoso

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 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
+* 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 [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.rst

@@ -0,0 +1,38 @@
+How to Contribute
+=================
+
+Contributions are welcome! Not familiar with the codebase yet? No problem!
+There are many ways to contribute to open source projects: reporting bugs,
+helping with the documentation, spreading the word and of course, adding
+new features and patches.
+
+Getting Started
+---------------
+#. Make sure you have a GitHub account.
+#. Open a `new issue`_, assuming one does not already exist.
+#. Clearly describe the issue including steps to reproduce when it is a bug.
+
+Making Changes
+--------------
+* Fork_ the repository on GitHub.
+* Create a topic branch from where you want to base your work.
+* This is usually the ``master`` branch.
+* Please avoid working directly on ``master`` branch.
+* Make commits of logical units (if needed rebase your feature branch before
+  submitting it).
+* Check for unnecessary whitespace with ``git diff --check`` before committing.
+* Make sure your commit messages are in the `proper format`_.
+* If your commit fixes an open issue, reference it in the commit message (#15).
+* Make sure your code comforms to PEP8_.
+* Make sure you have added the necessary tests for your changes.
+* Run all the tests to assure nothing else was accidentally broken.
+* Don't forget to add yourself to AUTHORS_.
+
+These guidelines also apply when helping with documentation (actually, for
+typos and minor additions you might choose to `fork and edit`_).
+
+Submitting Changes
+------------------
+* Push your changes to a topic branch in your fork of the repository.
+* Submit a `Pull Request`_.
+* Wait for maintainer feedback.