How to contribute
============================================

1. Open issues and tag them appropriately based on bug/feature request etc
2. Follow PEP-8 compliance for code review
3. `py.test` is used for testing, write integration/unit tests where necessary
4. +1 required by @csanders-git or @zmallen for merge
5. CI (eventually) required for merge 

FTW contributors (sorted alphabeticaly)
============================================

* **[Chaim Sanders](https://github.com/csanders-git)**

  * HTTP request/response parser
  * Rule Design

* **[Jared Stroud](https://github.com/jaredestroud/)**
  * HTTP Library

* **[Zack Allen](https://github.com/zmallen/)**

  * Rule design
  * Testing format
  * Framework refactoring
  * Error handling

How to contribute
============================================

1. Open issues and tag them appropriately based on bug/feature request etc
2. Follow PEP-8 compliance for code review
3. `py.test` is used for testing, write integration/unit tests where necessary
4. +1 required by @csanders-git or @zmallen for merge
5. CI (eventually) required for merge 

FTW contributors (sorted alphabeticaly)
============================================

* **[Chaim Sanders](https://github.com/csanders-git)**

  * HTTP request/response parser
  * Rule Design

* **[Ezekiel Templin](https://github.com/ezkl/)**

  * Other

* **[Jared Stroud](https://github.com/jaredestroud/)**
  * HTTP Library

* **[Zack Allen](https://github.com/zmallen/)**

  * Rule design
  * Testing format
  * Framework refactoring
  * Error handling


Add myself as a contributor
Add myself as a contributor
