From dae60e9a1fa14de00ce655de7948875038b3f877 Mon Sep 17 00:00:00 2001
From: Dominik Liebler <liebler.dominik@googlemail.com>
Date: Wed, 4 Sep 2013 10:11:18 +0200
Subject: [PATCH] added MIT license to README

---
 README.md | 39 ++++++++++++++++++++++++++++++++++-----
 1 file changed, 34 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index fdba274..b37b3a9 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# design patterns in PHP
+# DesignPatternsPHP
 
 [![Build Status](https://travis-ci.org/domnikl/DesignPatternsPHP.png?branch=master)](https://travis-ci.org/domnikl/DesignPatternsPHP)
 
@@ -6,9 +6,11 @@ This is a collection of known design patterns and some sample code how to implem
 
 I think the problem with patterns is that often people do know them but don't know when to apply which.
 
+## Patterns
+
 The patterns can be structured in roughly three different categories:
 
-## Creational
+### Creational
 
 * [AbstractFactory](AbstractFactory)
 * [Builder](Builder)
@@ -19,7 +21,7 @@ The patterns can be structured in roughly three different categories:
 * [Singleton](Singleton) (is considered an anti-pattern! :no_entry:)
 * [Multiton](Multiton) (is considered an anti-pattern! :no_entry:)
 
-## Structural
+### Structural
 
 * [Adapter](Adapter)
 * [Composite](Composite)
@@ -31,7 +33,7 @@ The patterns can be structured in roughly three different categories:
 * [DataMapper](DataMapper)
 * [DependencyInjection](DependencyInjection)
 
-## Behavioral
+### Behavioral
 
 * [ChainOfResponsibilities](ChainOfResponsibilities)
 * [Command](Command)
@@ -44,5 +46,32 @@ The patterns can be structured in roughly three different categories:
 * [TemplateMethod](TemplateMethod)
 * [Visitor](Visitor)
 
-*Please feel free to fork and extend existing or add your own examples!*
+## Contribute
+
+Please feel free to fork and extend existing or add your own examples and send a pull request with your changes!
+
+## License
+
+(The MIT License)
+
+Copyright (c) 2013 Dominik Liebler
+
+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.