The VDC initiative is now several months under way, and fantastic progress has been made. As part of this progress, in addition to making excellent progress toward making the codebase Drupal core-worthy, today we are announcing that Dries has promoted the project from a community initiative to an official initiative.
The team has grown significantly, and even though I haven’t personally been able to participate as much as would be liked, the team has more than made up for me. We are more or less on schedule to meet our goals.
First, as of the time of this writing the chipin is JUST shy of $7,500. Thanks to everyone who has contributed! This is a fantastic amount of money in a short time, but there's going to be a long way to go! Of course, I don't expect the chipin to be all of the funding, but for right now it's what we have. So please, help me spread this around!
It's funny. I had no plans to travel other than Drupalcon Denver this year and a family trip to Disneyland because the little one really does think it's the best place on Earth. Then I decided to ask Dries about Views in Core. Honestly, it's one of the scariest things I've done in years.
As a side effect, suddenly I'm travelling all over the place putting together sprints to ensure this thing gets done. I've already committed to a whole bunch, and am very close to committed to others. I am still looking for funding for some. Here is the Chaos World Tour list, as it stands:
At Drupalcon Denver, I approached Dries with the idea of putting Views into Drupal core for the Drupal 8 release. The idea was met very positively, and I've begun the work of putting together a team and resources and the things required to do this. Obviously, it's a big job, on the scale of initiatives like Mobile, CMI, WSCCI, etc.
This initiative will be called VDC, or Views in Drupal Core. The goal of this initiative is to put Views as we know it into Drupal core and properly integrate it so that everything is seamless. The fantastic UX work that Acquia funded last year already works very well with the core style, and we can continue to build on that to make it simply part of the Drupal experience.
For many years, large portions of the community have asked repeatedly why Views isn’t in core. Many of those answers are fading: Core’s processes are now capable of handling large projects. Views’ development needs have slowed as it has matured and gotten more feature-filled. It’s well known that Views and CCK, together, catapulted Drupal from having tens of thousands of installed sites to hundreds of thousands of installed sites by significantly reducing the amount of work needed to build complex functionality. CCK is in core now, but Views is not.
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.
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.