LICENSE and READMEs.

Author: mekras

CHANGELOG.md

@@ -0,0 +1,4 @@
+# Change Log
+
+
+## Unreleased

CONDUCT.md

@@ -0,0 +1,36 @@
+# Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of fostering an open and
+welcoming community, we pledge to respect all people who contribute through reporting issues,
+posting feature requests, updating documentation, submitting pull requests or patches, and other
+activities.
+
+We are committed to making participation in this project a harassment-free experience for everyone,
+regardless of level of experience, gender, gender identity and expression, sexual orientation,
+disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic addresses, without
+  explicit permission
+* Other unethical or unprofessional conduct.
+
+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. By
+adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently
+applying these principles to every aspect of managing this project. Project maintainers who do not
+follow or enforce the Code of Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces when an individual is
+representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an
+issue or contacting one or more of the project maintainers.
+
+This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org),
+version 1.2.0, available at
+[http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/).

CONTRIBUTING.md

@@ -0,0 +1,97 @@
+# Contributing
+
+If you're here, you would like to contribute to this repository and you're really welcome!
+
+
+## Bug reports
+
+If you find a bug or a documentation issue, please report it or even better: fix it :). If you
+report it, please be as precise as possible. Here is a little list of required information:
+
+ - Precise description of the bug
+ - Details of your environment (for example: OS, PHP version, installed extensions)
+ - Backtrace which might help identifing the bug
+
+
+## Security issues
+
+If you discover any security related issues, please contact us at
+[security@php-http.org](mailto:security@php-http.org) instead of submitting an issue on Github.
+This allows us to fix the issue and release a security hotfix without publicly disclosing the
+vulnerability.
+
+
+## Feature requests
+
+If you think a feature is missing, please report it or even better: implement it :). If you report
+it, describe the more precisely what you would like to see implemented and we will discuss what is
+the best approach for it. If you can do some research before submitting it and link the resources
+to your description, you're awesome! It will allow us to more easily understood/implement it.
+
+
+## Sending a Pull Request
+
+If you're here, you are going to fix a bug or implement a feature and you're the best! To do it,
+first fork the repository, clone it and create a new branch with the following commands:
+
+``` bash
+$ git clone git@github.com:your-name/repo-name.git
+$ git checkout -b feature-or-bug-fix-description
+```
+
+Then install the dependencies through [Composer](https://getcomposer.org/):
+
+``` bash
+$ composer install
+```
+
+Write code and tests. When you are ready, run the tests.
+(This is usually [PHPUnit](http://phpunit.de/) or [PHPSpec](http://phpspec.net/))
+
+``` bash
+$ composer test
+```
+
+When you are ready with the code, tested it and documented it, you can commit and push it with the
+following commands:
+
+``` bash
+$ git commit -m "Feature or bug fix description"
+$ git push origin feature-or-bug-fix-description
+```
+
+**Note:** Please write your commit messages in the imperative and follow the
+[guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) for clear and
+concise messages.
+
+Then [create a pull request](https://help.github.com/articles/creating-a-pull-request/) on GitHub.
+
+Please make sure that each individual commit in your pull request is meaningful. If you had to make
+multiple intermediate commits while developing, please squash them before submitting with the
+following commands (here, we assume you would like to squash 3 commits in a single one):
+
+``` bash
+$ git rebase -i HEAD~3
+```
+
+If your branch conflicts with the master branch, you will need to rebase and repush it with the
+following commands:
+
+``` bash
+$ git remote add upstream git@github.com:php-http/repo-name.git
+$ git pull --rebase upstream master
+$ git push -f origin feature-or-bug-fix-description
+```
+
+
+## Coding standard
+
+This repository follows the [PSR-2 standard](http://www.php-fig.org/psr/psr-2/) and so, if you want
+to contribute, you must follow these rules.
+
+
+## Semver
+
+We are trying to follow [semver](http://semver.org/). When you are making BC breaking changes,
+please let us know why you think it is important. In this case, your patch can only be included in
+the next major version.

LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2015 PHP HTTP Team <team@php-http.org>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is furnished
+to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.