CiviCRM DC Sprint – Drupal and Joomla and WordPress

We just returned from our first CiviCRM sprint. It was called the DC Sprint, but as Jeremy has already posted, we were actually in Maryland.

I was a first time attendee of a CiviCRM conference and sprint, so I really did not know what to expect. We were very pleased that both WordPress and Joomla! received some real attention at the sprint and we hope we are heading to a place where CiviCRM can be truly CMS agnostic.

WordPress CiviCRM installs can now benefit from WP-CLI tools. WP-CLI is a Drush equivalent for WordPress. We were able to merge Andy Walker’s port into 4.5 and Tim Otten added full API Explorer support for this. At the developer training day in DC on Saturday, we noticed an issue with civix and WordPress. This also fixed and now civix works with all CMSs without having to be directly tied to one as in the past. These two enhancements will help WordPress developers immensely.

Dana Skallman and I also worked through the unresolved tickets for WordPress. A great deal of progress has been made there, and in addition to all the new features in 4.5 users will find that the WordPress integration is better than ever.

What really made the sprint a great event were the people. We had three CMSes represented and while there was some good-natured kidding going on, it is clear to us that the community is focused on the CiviCRM project and supporting Drupal, Joomla! and WordPress.

We cannot wait to see the 4.5 release and we encourage everyone to participate in the CiviCRM Community. Whether you go to a meetup,  attend CiviCon in the spring or go to the next Code Sprint, you will not be disappointed and the community will be the better for it.