Kevin Bridges

I like to develop against local virtual hosts when I work with Drupal. Here is the apache httpd.conf configuration that has served me the best so far. The first VirtualHost is the default .. .simply replicate the second VirtualHost entry and edit accordingly. A simple edit of /etc/hosts to enter the virtual host name that matches the virtual host entries in the httpd.conf and a quick reload by apache and you are good to go. I particularly enjoy the independent logging for each site.

1. Generate a public/private key pair in your dev environment. Hit enter to accept the defaults. You will only ever need to run this once ... proceed to step two if you've already done this.
   $ ssh-keygen -t rsa
2. Copy keys to remote server. Substitute server in the code below with your target machine.
   $ ssh server "mkdir ~/.ssh; chmod 0700 ~/.ssh"
$ scp ~/.ssh/id_rsa.pub server:~/.ssh/authorized_keys2

It's official! The next Drupal Camp Colorado is happening the weekend of July 26th and 27th in Denver. Come join us in the mountains for two full days of Drupal wisdom and knowledge. We are going to host a mix of sessions and BOF's geared towards both the new Drupalers out there as well as the experienced veterans. Come join companies such as pingVision, Growing Venture Solutions, Aten Design Group, Blue Tent Marketing, Deproduction, and Civic Pixel among others.

To bad nobody listens

All great Drupal Camps leave participants thinking "what a great value" and "why not more" so to that end we have begun organizing a DBUG Camp in Denver/Boulder area of Colorado towards the last weekend in July. Many details will be forthcoming in the upcoming weeks, but for now I'd like to direct your attention to our Open Call for Logos ... yep, that's right ... we need help getting that killer logo put together so now is the time for you graphical types to shine!

Today was an amazing day in Paris. It's hard to imagine without the pictures, but we all gathered on the first floor of the facility that hosted yesterday's Drupal Camp. A good portion of yesterday was planning and thinking leaving today for massive amounts of hacking and coding. Charlie Gordon, Jimmy Berry, Roel De Meester, Erik Stielstra, Rok Žlender, Károly Négyesi, Miglius Alaburda, Dries Buytaert, Douglas Hubler, myself and our gracious host Ori Pekelman of AF83 gathered for more than 10 hours to solidify the framework that will help lead Drupal to it's next Killer Release.

Primary amongst todays developments was http://drupal.org/cvs?commit=111813 which brought a framework for functional tests to core. This is the culmination of "Three years, one month and twenty four days" according to Károly who also had this to say before he started dancing in his seat:
(12:24:52 PM) chx: YES YES YES YES YES YES YES
(12:24:54 PM) chx: YES YES YES YES YES YES YES
(12:24:54 PM) chx: YES YES YES YES YES YES YES
(12:24:55 PM) chx: YES YES YES YES YES YES YES

Today was the first official day of the Paris Code Sprint. Approximately 50-60 Drupalers from around the world gathered on the first floor to learn about and discuss Drupal while the sprinters gathered upstairs to solidify and unify our testing efforts. Ori Pekelman of AF83 has been a gracious and entertaining host providing the foundation for a good amount of discussion and coding.

pingVision has generously covered my airfare and hotel accomodations to ensure I am able to contribute to the Automated Testing Code Sprint happening in Paris this upcoming weekend. This is an important event that will help lay the foundation for Drupal's continued growth and evolution. It is a great responsibility and honor to be able to contribute and I look forward to helping make this effort a success. It is the continued effort of progressive companies like pingVision that help prove the Drupal Community is simply the best out there.

In addition, a special thanks goes to Greg Knaddison for his donation and support in this project ... there would simply be no Drupal without people like Greggles in the community.

Kieran just posted a great write-up on How to test 20 000 Drupal 7 core patches followed by Jimmy Berry's posting Paris Coding Sprint - Unit Testing. It summarizes many of the challenges Drupal is facing to be able to provide 100% testing coverage for Drupal core in addition to outlining the details of code sprint in Paris to help gather key developers to provide solutions.

During the code sprint, it is my goal to work closely with Rok Žlender to provide a mechanism for complete automated testing of HEAD in addition to a full reporting of the results in such a way that problems can be addressed and resolved. The issue queue at http://drupal.org/project/issues/Drupaltestbed will be cleaned up with specific resolutions being provided for issue http://drupal.org/node/239542, http://drupal.org/node/239546 and http://drupal.org/node/190987. Awareness of the Unit Testing Plan will need to be implemented into the Automated Testing as well.

[ begin rant ]
A few days ago I posted to the planet about an initiative underway to help get testing in place for core and I must say I am not entirely impressed by the response from the community. Take that with a grain of salt though because, naturally, the Drupal Community Rocks.

Here's the synopsis:
A) There is an organization of volunteers in place poised and ready to write the simpletests we need.
B) The only reason, that I see, they are not doing this is lack of feedback from the Drupal community.

All that you have to do is edit the wiki page at http://groups.drupal.org/node/9625 ... it's only 4 core modules we are all familiar with ... a few moments of your time. We've even taken the liberty of contributing the first set of scenarios that need testing as an example. Take a look at it ... even adding one line will help Drupal. I won't even start bugging you about contributing to the testing initiative regularly ... at least not yet.

What are you waiting for? Drupal needs you.
[ end rant ]