I've never really used a microframework in PHP before. I used Flask for a Python project that I did to experiment with using Google App Engine. The principles seem to be quite similar (although I will admit that having decorators in PHP would be ineresting) but the trade-off with a microframework is that you usually have to figure out an application layout for yourself.

He also uses the Pimple dependency injection container, Twig templating and Composer for package management. He describes how he got it all set up - organizing the code so Composer could understand it, creating the Twig templates directory and creating some of his default routes.

Despite the high expectations placed on them at times, developers are human. They were the last time we checked anyways. As humans, we are bound to make mistakes from time to time. And simple, common mistakes often slip past our filters the more comfortable we become with something. [...] But knowing what these common mistakes are and how to avoid them can really help speed up the development process and keep our clients smiling.

His list includes three big ones that, if forgotten, could end up being detrimental to your application (sooner or later) - poor housekeeping/organization of code, forgetting punctuation and forgetting to validate input from users.

You've heard about PHP namespaces by now. Most likely, you've heard about -- and likely participated in -- the bikeshedding surrounding the selection of the namespace separator. Regardless of your thoughts on the namespace separator, or how namespaces may or may not work in other languages, I submit to you several reasons for why I think namespaces in PHP are a positive addition to the language.

He breaks down his reasons into four different categories - the code organization benefits that come with namespace "containers", simplified interface structure, improved readability (no more huge class names) and a simpler method for identifying dependencies

I think the general idea of establishing a communication hub for core developers, end users and companies has been received with sufficient enthusiasm to start working on some of the boring details. The next logical step seems to be to start to fleshing out how the organization behind this communication hub should be structured. I want to leave as much power as possible with the individual members, which is one of the main reasons why I do not want companies to be come members.

He focuses on what he calls the "bootstrapping process" - the formation of the initial core group, opening the organization up for signups from the community, the creation of a constitution and the role of the core PHP developers in the group.

The fact of the matter is that today they [Zend] are stuck with a job they never asked to take over: They are the only PHP evangelism organization. So if you want to get some material on how to "sell" PHP to your Java loving IT department, Zend is the only real option to turn to. So we have to thank them for filling this void for now.

emPHPower is looking to replace that with a more diverse range of developers and companies that can provide details on a wide variety of PHP-related topics (including using PHP in the enterprise and the best open source solutions for different needs). He's looking to work with more of the regionally-focused PHP sites (user groups?) to help get things up and running in the beginning and then branching out to "the masses", possibly via other means.

I have been a member of a much smaller organization which adopted a similar mission. The reputation and livelihoods of this group had been damaged by years of infighting, bad legislation and no clear vision of of the future, not all of these are problems we face in the PHP community but the concepts behind organization are the same.

He notes that, being part of such groups previously, there are a few dos and don'ts to follow, specifically when it comes to community involvement.

WebMesh is a framework developed to serve of base for the creation of projects with PHP5. It offer an API with various abstractions to facilitate the application development and a module implementing the MVC pattern (Model2) using Smarty in the View.

Some of the goals for the framework include:

• Force a better organization of the your project classes
• Encorage the usage of the PHP version 5
• Becomes it a collaborative framework where others can contribute with new classes, abstrations, libraries, modules or frameworks to be integrated