This is a list of sessions I'll be attending at Drupalcon tomorrow:
A number of other sesions on Monday sound very interesting, but sadly I can't be in two places at once!
The sessions will cover how large organizations are involved with the open source project (like Google and IBM), how it can benefit any company (Profitable Web Development Process), where authentication systems are going today (OpenID and Identity), getting the speed you need (Performance Tuning), developing through automated testing (SimpleTest), how Flash can benefit from a backend system (Drupal and Flash/Flex), building AJAXy user interfaces (Drupal 6 AHAH), ensuring secure websites (Security), usability analysis (Administrator/User Friendliness), and much more.
I depart on Sunday afternoon from Toronto, and will be there Sunday night. I'll be wearing my Drupal Camp Toronto shirt, so I should be relatively easy to spot. I am looking forward to seeing you all in Boston!
Drupal 6 was released last week and everyone has been talking about how much greater it is than the previous release. I particularly like how powerful the new menu system is, the new caching and performance features, and all the new AJAXy goodness. But what is coming up next year in Drupal 7? This is a list of issues on Drupal.org that I am looking forward to see in the next release...
With these additions, and the implementation of a web service platform in core, we'll have ourselves a slick Drupal 7 release. What are you looking forward to in Drupal 7?
Now that Drupal 7 is open for development, people have started thinking about their personal battle plans for the next release. In the announcement, Dries mentioned the 11 wish list items that the community thought would make an excellent Drupal 7 release. I will be focusing, with Scott Nelson and the other Services people, on number 10: Better external APIs (import/export, webservices). Well, the Web Services part.
The Services module provides a slick API to implement common web services across a number of different protocols (XML-RPC, SOAP, REST, JSON, etc). Web services have become a very important part of how the websites interact with the user (think Flickr, Last.fm, Google, del.icio.us, etc). Getting parts of the Services module into core would mean that Drupal would have the ability to act more as a web service for external applications. It would allow Drupal to grow beyond the web, allowing interaction with the user in new platforms and in different ways.
Scott will be hosting a session on Services at DrupalCon 2008, so if you're interested in seeing where we'd like to see Services in Drupal 7, I think you should attend.
A while ago, I put together a very simple module named String Overrides. It provided an interface that used some new functionality in Drupal 6 to easily replace strings without the use of the locale or i18n modules. For a demonstration of how it works, check out the video. It was designed for Drupal 6 because it relied on locale_custom_strings_en, which is new to Drupal 6. If you have a look at the bottom of your settings.php, you'll see a note about it. There were many requests for a Drupal 5 version of String Overrides, but it was never put into implementation due to its reliance on this core functionality.
Well, the brilliant quicksketch fixed this, creating a very slick backport to Drupal 5. This backport was so elegantly made that it still even uses locale_custom_strings_en, which was actually only meant for Drupal 6. For details on how he did it, see his post about it. So, if you have a site running Drupal 5, and you want a quick and easy way to replace strings, String Overrides is good to go. Thanks, Nate!