New WordPress project structure

I’ve submitted maybe a few dozen patches to WordPress core, but must confess that I’ve never actually submitted tests for those patches. Part of the reason is that it’s not entirely intuitive, given that tests are managed in a completely separate repository.

That’s all about to change. A couple of weeks ago at WordCamp San Francisco, Koop approached a few of us with his idea for restructuring WordPress to have a “proper” project structure, with a real build system, integrated tests, moving compiled artifacts out of version control, etc. Basically, all the things that you would expect of a modern open source project, but which WordPress has lacked for historical reasons. Koop is a bit of a maven of great development tools and workflows (check out his amazing impromptu project he developed with Evan Solomon), so he’s absolutely the right person to be leading an effort like this.

So suffice it to say, I’m really excited that it was announced today that this project restructuring will happen for the WordPress 3.7 development cycle.

Have you written a response to this? Let me know the URL: