Some time ago, we formed the Views' Bug Squad and built up a group of people to help out in the Views' issue queue. At first this was a smashing success, and we did a great job of getting the Views' open issues queue down. For awhile. However, the realities of the busy-ness of the queue and my general hope to fire-and-forget didn't really work out, and activity in the Squad tailed off, though a couple of members remain quite active.

The following is a parody. It might be mildly offensive to some; if so, I apologize in advance.

Last year I officially went independent, turning Logrus into a boutique consulting shop specializing in the skills and knowledge I have to offer big players in the Drupal world. So far, things have gone fantastically well and it has allowed me to branch out a little more in the things I do, and has also helped fund several awesome projects that will benefit the community. Notably the Panelizer, Fieldable Panel Panes and ERS modules are completely funded by clients, as well as improvements to Panels such as the pane locking features.

The Panels In-Place Editor was a fantastic piece of functionality added to the Panels library, funded by Chapter Three (thanks!!!) and implemented almost entirely by Sam Boyer. This feature allows users to designate Panels of various types as editable in-place. This means that users with privileges are given a button at the bottom of the page which allows them to dynamically add, remove and rearrange content on that page. It's much more limited than the typical back end editor, but is much more usable by content managers who are focusing highly on the content.

EDIT: Comments on this post are now locked. Some jackhole came onto MY blog and insulted my wife. I cannot be fair, impartial or unbiased about that.

Full disclosure: I am a former Permanent Member of the Drupal Association. While I am no longer associated with the organization, I do have reasonably good knowledge of its inner workings and maintain contact with many people within the structure.

The modules page in Drupal has always been one of a handfull of pages that I consider flat out embarassing for us.

In the old days, i.e, back in Drupal 4.6 when I started, it was nothing more than a collection of modules, ordered alphabetically, with checkboxes. Drupal was small enough that this wasn't really that much of a problem. And then modules like ecommerce and CCK came along with these large collections of modules and nobody could find anything.

As of Jul 5, I've decided to try my luck on the open market, and am going freelance. I formed Logrus, Inc awhile back, and given the market right now, I feel like I can do pretty well as an independent provider. I have a very notable profile, I think.

I'm not severing my relationship with iO1 entirely; I'm staying on board as a contractor and will help them out, but my time is no longer exclusively theirs. Starting Jul 5, I will be available for the following types of tasks:

So I finally had a reason to upgrade Angry Donuts. Namely that Drupal 5 was holding me back from upgrading my webserver to PHP 5.3. So this is now running Drupal 7. Upgrading the theme was a pain in the buttocks, but everything else went smoothly, since I have almost no custom code here.

As a followup to yesterday's article about the new UI, this is a call for contributors.

Specifically:

1. We could use someone versed in CSS to help make the new UI look acceptable in Bartik and additionally it'd be nice if the 'base' version was at least usable in Stark. We're using a system where we can bring in stylesheets for specific things, so what we really want to do is provide some kind of basis for theme developers so that they can help tune the Views UI to their theme if they expect people to do administration in it.
   

Today, I merged the working branch for the Views 3 UX project into the 7.x-3.x branch of Views. This means that, as of midnight, GMT, everyone now has access to the completely retooled UI for Views, that was spearheaded by Acquia and specifically led by Jeff Noyes and Chris Brookins.

Note: To have access to this, please use the latest CTools -dev or latest CTools release. Some things in CTools had to be updated to support Views' use of export.inc.