We need to list all patterns sorted by groups in README.md
Just for better reference
Pull requests are welcome

There are few ways to manage files structure inside each pattern's php directory. Please vote.

1. Each example in it's own directory

└─┬ php/
  ├── composer.json
  ├── composer.lock
  ├─┬ example_car/
  │ ├── car.php
  │ └── car_test.php
  ├─┬ example_delivery/
  │ ├── delivery.php
  │ └── delivery_test.php
  └── vendor/

2. All examples in one dedicated directory:

└─┬ php/
  ├── composer.json
  ├── composer.lock
  ├─┬ example/
  │ ├── car.php
  │ └── delivery.php
  ├─┬ test/
  │ ├── car_test.php
  │ └── delivery_test.php
  └── vendor/

3. All examples in root directory:

└─┬ php/
  ├── composer.json
  ├── composer.lock
  ├── example_car.php
  ├── example_delivery.php
  ├─┬ test/
  │ ├── example_car_test.php
  │ └── example_delivery_test.php
  └── vendor/

I think we can remove all composer.json and all composer.lock files.
Originally I added them to have the ability to easily install PHPUnit right inside our repo, but as far as I see now, it's better to rely on having PHPUnit installed as a general dependency of our project.. as those files look like something that shouldn't be there. What do you think?

After we finish adding the most known patterns to our list, we need to provide a clear comparison of differences between similar ones, for example such patterns like:

• Facade and Gateway
• Decorator and Visitor
• etc.

This is very important as until now there is a big misunderstanding of what pattern should be used when and where. Also using wrong pattern may not necessary lead to a not working software, so it's very easy not to realize that a wrong pattern was used in particular case.

After such document will be started, it should be updated regulary with new patterns added.

I think we need to agree on a way we mention external resources in our works.

Here is my proposal:

• in README.md we should mention general resources we found helpful, like name of Book, name of Course, name of online resource like Wikipedia, StackOverflow, etc.
• in %pattern%/README.md we should mention resources we used to collect information on specific pattern, like URL of article on specific pattern, specific chapter of a book, post on StackOverflow, etc.

What do you think?

We need to find a free tool for easy generation of UML diagrams in SVG format

In order to keep Git tree growing in length and not in width which can make it hard to browse, I propose rebasing Pull Request against up-to-date master branch before merging if requested branch's HEAD is behind master's HEAD by more than 1 commit. As far as I know the best result is achieved if pull request initiator does that.
Please share your questions, thoughts on this topic here.

We need a clean way of collaboration for everyone who wants to contribute to our community-driven project. Here are some major issues we need to solve with it:

• Every addition/modification merged to master branch should pass a voting/discussing stage by group members
• Everyone should be able to propose/ask for addition/modification without sending a pull request
• Every group member should be notified about every addition/modification coming to the project

I think we should agree on the way we contribute. My proposal is to exclude any direct PUSHes, in order to avoid disagreement on anything that gets into master branch. Everything should go through Pull Request, even if it is one word replacement.

What do you think?

After adding most known patterns to our list and having enough README files in place, we'll need to overview the format of README file we want to stick to and propose a single prototype that will be used across all README files.

Consistency in Documentation across all patterns is important because:

• it's easier to read/understand/get used to one format of documentation
• it can be automatically parsed by script in the future (for a project's website?)