Following up on my PIFT 6.x-2.7 Released post, I'd like to take a moment to walk you through another new feature which was introduced with the rollout of the new code.
But before I do, a public service announcement: The 'enable project testing' checkbox has now been enabled for all contrib projects! To enable automatic testing of patches for your contrib project, visit the 'Edit -> Issues' subtab on your project page; the checkbox can be found under the 'testing' fieldset.
We are pleased to announce that PIFT 6.x-2.7 has been released, and is now deployed on Drupal.org. PIFT stands for 'project issue file test', and is the d.o component of Drupal's automated testing infrastructure. This latest release introduces a couple of exciting new features for project maintainers and patch writers, and you may notice some changes to your patch status messages over the next few days as a result ... read on to learn more about the first of these changes and what it means to you.
We had just shy of a dozen people get together for a BoF meet at BADCamp last weekend. This post summarizes what was discussed, some new ideas which were identified, and what we see as some of the next steps in the Project Application Process evolution.
This is the second post in series regarding Drupal's New Project Application process. The other posts in this series can be found here: Part 2 Part 3
Over the course of the next few days, hundreds of Drupal enthusiasts will be hopping on planes and heading to London to attend DrupalCon 2011. Unfortunately, I will not ... which means I won't be there for webchick and hejrocker's 'Project Application Process Revisited' core conversation.
As mentioned in this blog's first post, my experience with Drupal's "Project Application Process" is the catalyst which spurred my increased involvement within the Drupal community. As a new Drupal contributor, I found the process painful and extremely de-motivating.
Despite the best efforts of a small group of volunteers, the application backlog has grown to the point where applications may sit for weeks before an initial review, and some may go months from initial ticket to resolution. In the interest of improving this experience for future contributors, I joined the Code Review group on g.d.o ... and as the group members can tell you, I have plenty of thoughts to share on the topic.
Okay, I'll admit it ... PIFR isn't the sexiest, flashiest, or most widely used Drupal module in existence. In fact, if one were to try and identify the number of actual production sites using PIFR today, it'd be a tough job to use up all the fingers on one hand. Counting the number of people who can explain exactly how PIFR performs its magic would likely result in an even smaller total. However, these numbers paint a misleading picture ...