The Art Institute of Chicago (AIC) is one of the world's premier art museums, best-known for its collections of Impressionist, Post-Impressionist, and American paintings. In addition to housing famous paintings such as Seurat's A Sunday Afternoon on the Island of La Grande Jatte, van Gogh's Bedroom in Arles and Grant Wood's American Gothic, the Museum also has world-class collections of photography, arms and armor, ceramic figures, portrait sculptures, miniatures, and galleries of ancient Egyptian, Greek, and Roman artifacts, including the mummy of Paankhenamun.

Palantir.net has worked with AIC since 2005, when we helped them develop and implement their site redesign and CMS integration. Their existing site only showed a small selection of material from their collection; the goal of this project was to integrate the site with their backend asset management system to allow users to browse the Museum's entire collection online, as well as allow the Museum to quickly and easily create micro-sites to promote exhibitions.

Palantir worked on the AIC Collections site in collaboration with design partner Studio Blue, who provided the original design direction for the AIC Web site. Larry Garfield (Crell) and Colleen Carroll were the joint architects of the site, with Larry working as lead programmer and Colleen as lead themer. Tiffany Farriss provided strategic leadership for the project.

Earlier this week we have closed our special 80 Euro early bird offer with 335 registered participants! A great big thank you to all the people that already signed up!

With 8 more weeks to go we thought it was a good time to do some preliminary evaluation about our progress. We took the sign-up data from the past four Drupalcons and compared that with what we have so far. As was to be expected there has been some "nice action" in the last week of the first early bird offer. (Note that the registration was twice as long in Barcelona, so the numbers shown here are the sums from week 1 and 2; 3 and 4; 5 and 6).

In our third week we had 185 new sign ups of which over a hundred happened on the last day of the early bird offer. We didn't achieve Sunnyvale's peak signups of week two (212 signups), but our total of 335 registered participants did set a new record for the total amount of participants registered after three weeks of registration!

We are excited to announce that three key modules, Views, CCK, and Organic Groups, have published release candidates today, ready for testing. If you are interested in speeding the transition to a full release, install and test the Release Candidates (RC). Many months of work have gone into extensive rewrites of these modules, leading to major improvements that will make Drupal 6 an even more attractive platform for building websites.

As always, you should upgrade these modules on a test site first, and make sure to make a complete backup. You never know how your site's customizations will affect things, or what silly little thing nobody else caught.

IMPORTANT! There are a couple Drupal core bugs that could affect anyone using Views and anyone updating from an earlier version of CCK. They are fixed in the Drupal 6.3 release, please use that.

More details about these pivotal module releases follow...

Understanding Drupal is the first video in The Lullabot Learning Series. This video provides an overview of Drupal as a content management system, as a PHP web application framework, and as a developer community. Its documentary-style exploration covers all the terminology and fundamental concepts for both site administrators and developers. If you've ever been confused by Drupal or are still trying to wrap your head around the community and platform, this video is intended as a roadmap to accelerate your journey up the Drupal learning curve.

Lullabots Addison Berry (add1sun), Angela Byron (webchick), Jeff Eaton (eaton), Nathan Haug (quicksketch), Jeff Robbins (jjeff), James Walker (walkah), and Matt Westgate (matt westgate) sit down to tell us about Drupal in this video directed and edited by Kent Bye (kentbye). A portion of the profits from this video will be donated directly to the Drupal Association.

Topics include...

The Interaction Design and Information Architecture program at the University of Baltimore and a team of eight graduate students in the Research Methods class, taught by professor Kathryn Summers, have completed a usability study on Drupal. The Drupal community has been working with Becca Scollan in the usability group.

The usability research used video recordings and eye tracking tools to follow participants gaze in the Drupal interface. The study used eight participants, which is considered a valid sample. The study duplicated some tests done in usability testing at the University of Minnesota, and confirmed several results.

Fixing the usability problems

Core issues from both studies

• WYSIWYG in core: WYSIWYG group, Better input format support in Drupal 7
• Evaluators said that "content" was used too often in too many contexts and that was confusing: content, post, node , Change "story" content type to "article" or "news", Content types descriptions tweaks

For the past year or so, there have been periodic questions raised about Drupal's licensing status. Is it GPL version 2? Are we moving to GPL version 3? Could we even if we wanted to? Is it OK to write a module that does [something weird]? As a member of the Drupal Association Board of Directors, I made it my task to sort out the answers to those questions.

Understanding licensing, and the differences between licenses, is more important than some realize. Open source is not the same as public domain. Open source and Free Software requires that source code be made available and that others are allowed to make use and share of the source code, but there are rules attached to how they can do so just as there is with proprietary software. For example, not all open source software can be combined, and there are requirements for how you distribute the source code of a program. Knowing which of those rules apply to Drupal, and to Drupal modules and themes, is important not only for the health of the code base (so we know what we can and can't do with the work of over a thousand people) but also to the health of the growing commercial Drupal economy.

I am pleased to announce that we now do have firm answers to these questions, and have a new and shiny FAQ up to answer them. There is nothing new in the FAQ; it is just a clarification of some edge cases that didn't used to exist.

We'd like to thank James Vasile of the Software Freedom Law Center for his help in working out the details. We also wanted to take a few moments to go into some of the reasoning behind how we reached a few of these conclusions.