update

.github/CODEOWNERS

@@ -9,14 +9,17 @@ community/hello_world/*/* @quantumjim
 community/games/* @quantumjim
 community/games/*/* @quantumjim
 
-community/terra/* @attp
-community/terra/*/* @attp
-community/algorithms/* @attp
+community/terra/* @attp @ajavadia
+community/terra/*/* @attp @ajavadia
+community/algorithms/* @attp @ajavadia
 
 community/aqua/* @chunfuchen @pistoia
 community/aqua/*/* @chunfuchen @pistoia
 community/aqua/*/*/* @chunfuchen @pistoia
 
-community/teach_me_qiskit_2018/* @rraymondhp
-community/teach_me_qiskit_2018/*/* @rraymondhp
+community/awards/teach_me_qiskit_2018/* @rraymondhp
+community/awards/teach_me_qiskit_2018/*/* @rraymondhp
+
+community/ignis/* @dcmckayibm
+qiskit/ignis/* @dcmckayibm
 

.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 qiskit@qiskit.org. 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 qiskit@qiskit.org.
+

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,33 @@
+---
+name: "\U0001F41B Bug report"
+about: "Create a report to help us improve \U0001F914."
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+<!-- ⚠️ If you do not respect this template, your issue will be closed -->
+<!-- ⚠️ Make sure to browse the opened and closed issues -->
+
+### Informations
+
+- **Qiskit version**:
+- **Python version**:
+- **Operating system**:
+
+### What is the current behavior?
+
+
+
+### Steps to reproduce the problem
+
+
+
+### What is the expected behavior?
+
+
+
+### Suggested solutions
+
+

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,10 @@
+---
+name: Documentation
+about: 'Create a report to help us improve the documentation '
+title: ''
+labels: documentation
+assignees: ''
+
+---
+
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,15 @@
+---
+name: "\U0001F680 Feature request"
+about: "Suggest an idea for this project \U0001F4A1!"
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+<!-- ⚠️ If you do not respect this template, your issue will be closed -->
+<!-- ⚠️ Make sure to browse the opened and closed issues to confirm this idea does not exist. -->
+
+### What is the expected behavior?
+
+

.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
+
+

INSTALL.md

@@ -9,17 +9,10 @@
 
 **Get the tutorials**<BR>
 
-For the full experience, you can start by [downloading](https://github.com/Qiskit/qiskit-tutorial/archive/master.zip) the tutorials. Unzip the archive in the directory of your choice (this is the recommend way). Alternatively, the more advanced user may choose to use `git`. If you have `git` installed, run
-
-```
-git clone https://github.com/Qiskit/qiskit-tutorial.git
-```
+For the full experience, you can start by downloading the latest release of the tutorials from [here](https://github.com/Qiskit/qiskit-tutorials/releases). Unzip the archive in the directory of your choice (this is the recommend way). 
 
 To properly view and run the tutorials, you will need to install [Jupyter Notebook](https://jupyter.readthedocs.io/en/latest/install.html).
 
-If you need to install `git` follow the instructions [here](https://help.github.com/articles/set-up-git/).
-
-
 ## 2. Install Qiskit, Qiskit Aqua and Qiskit Aqua Chemistry
 
 At least [Python 3.5 or later](https://www.python.org/downloads/) is required to install and use Qiskit. If you have multiple Python versions installed (and particularly if the command `python --version` returns an incompatble version), you will need to ensure that your versions are [managed correctly](https://conda.io/docs/user-guide/tasks/manage-python.html). This can be done using the `environment.yml` file, as detailed below.

README.md

@@ -1,33 +1,25 @@
-
-<img src="images/qiskit-heading.gif" >
-
-***
-
-
 # Qiskit Tutorials
 
-[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
-[![Binder](https://mybinder.org/badge.svg)](https://mybinder.org/v2/gh/QISKit/qiskit-tutorial/master?filepath=index.ipynb)
-
+[![License](https://img.shields.io/github/license/Qiskit/qiskit-tutorials.svg?style=popout-square)](https://opensource.org/licenses/Apache-2.0)[![](https://img.shields.io/github/release/Qiskit/qiskit-tutorials.svg?style=popout-square)](https://github.com/Qiskit/qiskit-tutorials/releases)
 
-Welcome to the [Qiskit](https://www.qiskit.org/ tutorials!
+Welcome to the [Qiskit](https://www.qiskit.org/) tutorials!
 
 In this repository, we've put together a collection of Jupyter notebooks aimed at teaching people who want to use Qiskit for writing quantum computing programs, and executing them on one of several backends (online quantum processors, online simulators, and local simulators). The online quantum processors are the [IBM Q](https://quantumexperience.ng.bluemix.net/qx/devices) devices.
 
-## Installation and Setup
+## Installation
 
 The notebooks for these tutorials can be viewed here on GitHub. But for the full experience, you'll want to interact with them!
 
-The easiest way to do this is using [the Binder image](https://mybinder.org/v2/gh/Qiskit/qiskit-tutorial/master?filepath=index.ipynb), which lets you use the notebooks via the web. This means that you don't need to download or install anything, but it also means that you should not insert any private information into the notebooks (such as your API key). We recommend as pointed out in [issue #231](https://github.com/Qiskit/qiskit-tutorial/issues/231) that after you are done using mybinder that you regenerate your token.
+The easiest way to do this is using [the Binder image](https://mybinder.org/v2/gh/qiskit/qiskit-tutorials/master?filepath=index.ipynb), which lets you use the notebooks via the web. This means that you don't need to download or install anything, but it also means that you should not insert any private information into the notebooks (such as your API key). We recommend as pointed out in [issue #231](https://github.com/Qiskit/qiskit-tutorials/issues/231) that after you are done using mybinder that you regenerate your token.
 
 Please refer to this [installation guide](INSTALL.md) for setting up Qiskit and the tutorials on your own machine (this is the recommended way).
 
-***
-
 ## Contents
+
 We have organized the tutorials into two sections:
 
 ### 1. [Qiskit notebooks](qiskit/)<a id='qiskit'></a>
+
 We've collected a core reference set of notebooks in this section outlining the features of Qiskit. We will be keeping them up to date with the latest Qiskit version.  
 - [Basics](qiskit/basics) is meant for those who are getting started.
 - [Terra](qiskit/terra) is meant for those who want to study circuits.
@@ -36,26 +28,29 @@ We've collected a core reference set of notebooks in this section outlining the
 - [Jupyter](qiskit/jupyter) is meant to highlight some cool Juypter features.
 
 ### 2. [Community notebooks](community/)<a id='community'></a>
+
 Teaching quantum computing and qiskit has many different paths of learning. We love our community, and we love the contributions so keep them coming. Because Qiskit is changing so much, at the moment we cant keep this updated, but there are some great notebooks in here. See:
 - [Hello, Quantum World](community/hello_world/) learn from the community how to write your first quantum program.
 - [Quantum Games](community/games/), learn quantum computing by having fun.
 - [Quantum Information Science with Terra](community/terra/), learn about quantum information science with Qiskit Terra.
 - [Textbook Quantum Algorithms](community/algorithms/), learn Qiskit from the textbook algorithms.
 - [Quantum Algorithms](community/aqua/), learn about quantum algorithms for noisy near-term devices with Qiskit Aqua.
-- [Teach Me Qiskit 2018](community/teach_me_qiskit_2018/), learn from the great contributions to the [Teach Me Qiskit award](https://www.ibm.com/blogs/research/2018/06/teach-qiskit-winner/).
+- [IBM Q Awards](community/awards/), learn from the great contributions to the [IBM Q Awards](https://qe-awards.mybluemix.net/), [Teach Me Qiskit 2018](community/awards/teach_me_qiskit_2018/index.ipynb) and [Teach Me Quantum 2018](community/awards/teach_me_quantum_2018/index.ipynb).
 
 To go through the tutorials, load up the [index.ipynb](index.ipynb) notebook and start learning.
 
-***
+## Contribution Guidelines
 
-## Contributing
-If you would like to contribute to the tutorials, there are a number of ways to get involved:
+If you'd like to contribute to Qiskit Tutorials, please take a look at our
+[contribution guidelines](.github/CONTRIBUTING.md). This project adheres to Qiskit's [code of conduct](.github/CODE_OF_CONDUCT.md). By participating, you are expect to uphold to this code.
 
-* **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 request](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.
+We use [GitHub issues](https://github.com/Qiskit/qiskit-tutorials/issues) for tracking requests and bugs. Please use our [slack](https://qiskit.slack.com) for discussion and simple questions. To join our Slack community use the [link](https://join.slack.com/t/qiskit/shared_invite/enQtNDc2NjUzMjE4Mzc0LTMwZmE0YTM4ZThiNGJmODkzN2Y2NTNlMDIwYWNjYzA2ZmM1YTRlZGQ3OGM0NjcwMjZkZGE0MTA4MGQ1ZTVmYzk). For questions that are more suited for a forum we use the Qiskit tag in the [Stack Exchange](https://quantumcomputing.stackexchange.com/questions/tagged/qiskit).
 
-## Contributors
-These tutorials are the work of our [Qiskitters](https://github.com/Qiskit/qiskit-tutorial/graphs/contributors) who contribute to the project at different levels.
+## Authors and Citation
+
+Qiskit Tutorials is the work of [many people](https://github.com/Qiskit/qiskit-tutorials/graphs/contributors) who contribute
+to the project at different levels. If you use Qiskit, please cite as per the included [BibTeX file](https://github.com/Qiskit/qiskit/blob/master/Qiskit.bib).
 
 ## License
-This project is licensed under the Apache License 2.0 - see the [LICENSE](https://github.com/QISKit/qiskit-tutorial/blob/master/LICENSE) file for details.
+
+[Apache License 2.0](LICENSE.txt)