Changes to maintainers list for readability:

- Added Responsibilities of Maintainers to MAINTAINERS.md
- Moved Contributors section of README.md to be in MAINTAINERS.md
- Added Contact Us section

README.md

@@ -51,12 +51,8 @@ limitations under the License.
 10. [Thank You](#thank-you)
 
 ## Overview
-<<<<<<< Updated upstream
 
 **The Snap Telemetry Framework** is a project made up of multiple parts: 
-=======
-![workflow-collect-process-publish](https://cloud.githubusercontent.com/assets/1744971/14644683/be49a6b6-0607-11e6-8621-14f7b54e2192.png)
->>>>>>> Stashed changes
 
 * A hardened, extensively tested daemon, `snapteld`, and CLI, `snaptel` (in this repo)
 * A growing number of maturing `plugins` (found in the [Plugin Catalog](#plugin-catalog))
@@ -335,7 +331,7 @@ Add to the ecosystem by building your own plugins to collect, process or publish
 ### Become a Maintainer
 Snap maintainers are here to help guide Snap, the plugins, and the community forward in a positive direction. Maintainers of Snap and the Intel created plugins are selected based on contributions to the project and recommendations from other maintainers. The full list of active maintainers can be found [here](docs/MAINTAINERS.md).
 
-Think you're ready to be a maintainer? Check out [Responsibilities of a Maintainer](docs/MAINTAINERS.md#responsibilities-of-maintainers) and open an issue on github to discuss your interest.
+Interested in becoming a maintainer? Check out [Responsibilities of a Maintainer](docs/MAINTAINERS.md#responsibilities-of-maintainers) and open an issue [here](https://github.com/intelsdi-x/snap/issues/new?title=interested+in+becoming+a+maintainer&body=About+me) to discuss your interest.
 
 ## Code of Conduct
 All contributors to Snap are expected to be helpful and encouraging to all members of the community, treating everyone with a high level of professionalism and respect. See our [code of conduct](CODE_OF_CONDUCT.md) for more details.

docs/MAINTAINERS.md

@@ -0,0 +1,54 @@
+# Maintainers
+
+Among our many awesome contributors, Snap has a great team of maintainers. Maintainers are expected to have a solid understanding of Snap and are here to help guide Snap, the plugins and the community forward in a positive direction.  
+
+All maintainers and members of the community are expected to be helpful and encouraging. Treating everyone with a high level of professionalism and respect is a top priority for us. See our [CODE_OF_CONDUCT](../CODE_OF_CONDUCT.md) for further explanation of our policies.
+
+If you're interested in joining the team as a maintainer, check out the [becoming a maintainer](../README.md#become-a-maintainer) section of our README. 
+
+----
+
+## Technical Lead: Joel Cooklin (@jcooklin)
+While our maintainers guide Snap, the plugins, and the community forward in a positive direction, our technical lead, Joel, is the key decision maker and fearless leaders for all of us. If there is ever a debate within the project, Joel is the tiebreaker. 
+
+## Snap Maintainers
+Below is the list of Snap Maintainers, they are largely responsible for approving pull requests and thus have the final say on coding style and implementation. 
+
+| Name              | Tag                |
+|:------------------|:-------------------|
+| Andrzej Kuriata   | @andrzej-k         |  
+| Cody Roseborough  | @IRCody           s |  
+| Emily Gu          | @candysmurf        |  
+| Izabella Raulin   | @IzabellaRaulin    |  
+| Joel Cooklin      | @jcooklin          |  
+| Katarzyna Kujawa  | @katarzyna-z       |  
+| Kelly Lyon        | @kjlyon            |  
+| Lukasz Mroz       | @lmroz             |  
+| Marcin Krolik     | @marcin-krolik     |  
+| Marcin Olszewski  | @marcintao         |  
+| Marcin Spoczynski | @sandlbn           |  
+| Maria Rolbiecka   | @mkuculyma         |  
+| Mateusz Kleina    | @mkleina           |  
+| Matt Brender      | @mjbrender         |  
+| Nicholas Weaver   | @lynxbat           |  
+| Olivier Cano      | @kindermoumoute    |  
+| Patryk Matyjasek  | @PatryMatyjasek    |  
+| Rashmi Gottipati  | @rashmigottipati   |  
+
+### Responsibilities of Snap Maintainers
+Maintainers are expected to contribute regularly in at least one of the following capacities:
+* Direction/Design: Meaningfully contributing to RFC or design comments
+* Code Contributions: Submitting pull requests for either bug fixes or features
+* Support: Active participation in a support role in some form (code reviews, addressing questions, triaging issues)
+
+If a maintainer is consistently unable to perform the above actions they will be asked to withdraw from the maintainer group. This does not preclude them from becoming a maintainer at a later date.
+
+## Initial Authors
+All contributors are equally important to us, but we would like to thank the [initial authors](AUTHORS.md#initial-authors) for helping make open sourcing Snap possible.
+
+## Contact Us
+Contacting us is easy! Use these simple tips for the most effective communication with us.
+* **For a quick question:** reach out to us on [Slack](https://intelsdi-x.herokuapp.com/). You can search by GitHub handles and ping individual users, start a group conversation, and post to the Snap community. Maintainers check this regularly and will be the fastest way of contacting us.
+* **If you find a bug in the code or have a question about some code:** go ahead and [open up a GitHub issue](https://github.com/intelsdi-x/snap/issues). This will start a dialog. If you don't know how to solve the issue we will pick it up and help fix the bug. 
+* **To get a specific person's attention:** @mention them in an issue and they will get back to you.
+* **For plugin related issues:** contact the plugin's author or reach out to a maintainer.