This month’s top events (July 2 – August 5)**
A handpicked selection of some of the most exciting PHP events from around the world
London Google Glass Creative Kickoff Meet
July 4 // London, UK // Free
The UK capital is the latest to get a meetup group dedicated to Google’s new wearable computing gadget.
July 5-6 // Madrid, Spain // €200
A non-profit, volunteer-driven event, Spain.js sees talks from Robert Nyman, editor of the Mozilla Hacks blog and Douglas Crockford on “Syntaxation”.
php-ist: Istanbul PHP Conference
July 6 // Istanbul, Turkey // Free
A one-day conference taking place in Yildiz Technical University. Talks on Symfony, PHPUnit and Scaling PHP in Public Offices.
16 – 19 July // Orlando, FL, USA // $1495
Sencha Touch users may be interested in the company’s annual event, which includes over 60 technical sessions and opportunities to speak to Sencha engineers.
San Diego PHP Meetup
July 24 // Carlsbad, CA, USA // Free
At this month’s meetup, ScrumMaster Tim Sorweid goes through the basics of agile development in a talk called “It’s the Features, Stupid: How scrum helps deliver features on time”.
To get your event featured in our calendar, email firstname.lastname@example.org.
Open source spotlight: PHPCI
Meeting the people behind the most exciting homegrown OSS projects. This month, we speak to Dan Cryer about PHPCI, a continuous integration tool “specifically designed for PHP”.
WPM: Who’s behind PHPCI?
Cryer: Before „going public“ with the project, all of the development was done by me, funded by the company I run, Block 8 (http://www.block8.co.uk). However since releasing the Alpha version a few weeks ago, we’ve had some significant contributions from a few other developers, most notably from Github users gabriel403, kamermans and meadsteve.
Why did you decide to start it?
PHPCI started out as just a pet project of mine, as I’ve never found a good CI tool for PHP. Sure, you can use Jenkins, but it really is not an enjoyable tool to look at or use, and it’s a royal pain to set up!
How is it designed specifically for PHP?
PHPCI is designed from the ground up to be specifically for PHP – It integrates PHP testing tools like PHP Unit, PHPMD and PHP Spec as first class citizens, rather than as add-ons that you can install manually. It was built by PHP developers, for PHP developers and it was built in PHP to boot.
How close to being production-ready is it?
Realistically, it is production ready now, it is being used by hundreds of developers already. We’re very close to releasing a beta version, there are just a few more features we want to get in place before we do so, such as success/failure notification support. From there, once we’re happy that the beta is stable, we’ll call it 1.0.
How can people get involved, and what can they do to help out?
From the beginning, I wanted to make sure that the PHPCI project was one that people could feel comfortable contributing to. All too often, open source projects make it unnecessarily difficult or unpleasant for people to get involved. The easiest way to „do your bit“ with PHPCI is to run it, test it and report any bugs you come across – we really value that feedback.
If you want to get a bit more deeply involved, you could:
- Try and fix a bug / implement a feature you’ve found in the Github issue tracker.
- Create a new plugin to support a testing tool we haven’t covered yet.
- Work on improving the UI or add additional reporting functionality to builds.
Where do you hope to see the project in a year’s time?
Naturally the first goal is to get a stable 1.0 release out and see how developers take to it. I’d really like to see PHPCI used as extensively as the tools that it supports (PHPUnit, PHPMD, PHPCS and so on.)
From there, I have a few key features I’d like to implement, including the ability to run builds on a set of servers (so for example to test PHP 5.3, 5.4 and 5.5 simultaneously,) and to be able to launch Vagrant VMs to run tests in.
Features like that would be optional of course, as the primary goal is to have a testing tool so easy to set up and use that PHP developers have no excuse but to test their code!