Added codeowners and PR template

Author: abraham.asfaw

.github/CODEOWNERS

@@ -0,0 +1,20 @@
+# Fallback codeowners for all files that do not have an explicit rule.
+* @jaygambetta @aasfaw
+
+# Codeowners for individual folders
+terra/**/* @nonhermitian @attp @aasfaw @quantumjim @rraymondhp
+algorithms/* @attp @aasfaw @quantumjim @rraymondhp
+
+aer/* @chriseclectic @attp @aasfaw @quantumjim @rraymondhp
+ignis/* @dcmckayibm @yehuda-naveh @attp @aasfaw @quantumjim @rraymondhp
+
+aqua/**/* @chunfuchen @pistoia @aasfaw
+artificial_intelligence/**/* @chunfuchen @pistoia @aasfaw
+chemistry/**/* @chunfuchen @pistoia @aasfaw
+finance/**/* @chunfuchen @pistoia @aasfaw
+optimization/**/* @chunfuchen @pistoia @aasfaw
+
+arts/* @attp @aasfaw @quantumjim @rraymondhp
+awards/**/* @attp @aasfaw @quantumjim @rraymondhp @pistoia
+games/**/* @attp @aasfaw @quantumjim @rraymondhp
+hello_world/**/* @quantumjim @aasfaw

.github/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/

.github/CONTRIBUTING.md

@@ -0,0 +1,33 @@
+# Contributing
+
+If you would like to contribute to the Qiskit-tutorials, there are a number of ways to 
+get involved:
+
+* **Issues**: Issues can be reported with GitHub [issue
+  reporting](https://github.com/Qiskit/qiskit-tutorial/issues) for this repository. 
+  Select `New issue`, fill in a descriptive title, and provide as much detail 
+  as is needed for the issue to be reproduced.
+
+* **Notebooks**: If you would like to contribute a notebook, please 
+  create a [fork](https://help.github.com/articles/fork-a-repo/) of the repository 
+  from the `master` branch and create a 
+  [pull requests](https://help.github.com/articles/about-pull-requests) for your change.
+  Note that new notebooks should be placed in the relevant part of the 
+  [Community](./community/) section.
+
+## Contributor License Agreement
+
+We'd love to accept your code! Before we can, we have to get a few legal
+requirements sorted out. By having you sign a Contributor License Agreement (CLA), we
+ensure that the community is free to use your contributions.
+
+When you contribute to the Qiskit project with a new pull request, a bot will
+evaluate whether you have signed the CLA. If required, the bot will comment on
+the pull request,  including a link to accept the agreement. The
+[individual CLA](https://qiskit.org/license/qiskit-cla.pdf) document is
+available for review as a PDF.
+
+If you work for a company that wants to allow you to contribute your work,
+then you'll need to sign a [corporate CLA](https://qiskit.org/license/qiskit-corporate-cla.pdf)
+and email it to us at [email protected].
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+<!--
+⚠️ If you do not respect this template, your pull request will be closed.
+⚠️ Your pull request title should be short detailed and understandable for all.
+⚠️ Also, please add it in the CHANGELOG file under Unreleased section.
+⚠️ If your pull request fixes an open issue, please link to the issue.
+
+✅ I have added the tests to cover my changes.
+✅ I have updated the documentation accordingly.
+✅ I have read the CONTRIBUTING document.
+-->
+
+### Summary
+
+
+
+### Details and comments
+
+