The University of Minnesota has graciously offered us another opportunity to gather data and insights from observing smart people using Drupal for the first time.
If you want to contribute actual changes to the Drupal software, you have to do it through patches. Patches are a kind of text file that describe the changes in a way that lets them easily be applied to the official code base. To create them, you have to jump through a couple of hoops, especially checking out Drupal head from CVS and creating the actual patch from the changes you made.
“…Surgical teams that follow a basic checklist in the operating room, from discussing expected blood loss to confirming the patient's name, reduced the rate of deaths and complications by more than a third.” (source)
Drupal module development will hopefully not cost human lives one way or the other. But when building your module's UI the same principle is at work. It's all too easy to skip the basics, and go straight for the more complex parts of the problem. That’s the interesting part after all.
The modules page is a typical example of a long list that gets hard to manage pretty quick. The categorization is not ideal, with big modules providing their own category and a quickly growing 'misc' section.
Talking for two days straight during Utrecht Ux sprint ruined my voice, but it did accomplish an important thing: Somewhere on Sunday morning, Dries, Mark, Leisa, Bojhan and me finally got to a point that we knew and understood that we w
Everybody seemed to have read and understood most of the briefing email and sprint website because there we were, 20+ Drupal peeps showing up at the lovely OneShoe office, on time.
