60 minutes

Overview

For D6, the imagefield_crop module will be abandoned and Yuval Hager (Yhager) and Kristof De Jaeger (swentel) are joining forces to port Imagecache javascript crop module to D6 and make a top rock module. For this we need to sit down together and come up with a battle plan but also encourage other people to join in. We can use everybody: themers, javascript guru's, UI wizards and php cooks. Join us if you are interested or simply to suggest features for D6.

Resources

http://drupal.org/project/imagecrop
http://drupal.org/project/imagefield_crop
http://drupal.org/project/imagecache

Overview

Since the drupal world is constantly growing with more and more (non-)commercially oriented projects and people starting off, I thought it was time to come up with a platform that tries to connect projects (as well as staffing requests), people (drupalists) and knowledge. As of now I am in the final stage of launching this non-commercial platform, called drupaleo, as a beta version.

Agenda

Goals

Resources

clear mind required

Overview

A "Cloud" offers a virtualized datacenter infrastructure that allows you to build your own network applications. In this session, we'll cover an approach to implementing Drupal in the cloud using the popular Amazon Web Services as the cloud service.

Agenda

What with this cloud stuff?

An overview of what clouds are and what they're good for.

Drupal on Amazon Web Services

APIs, tools, and techniques.

Persistence issues and solutions

Where to store /files & database backups.

Cluster management overview

Clusters go great with clouds. Here's some cluster tools and services, some cloud specific some not.

High availability in the cloud

The issue of reliability in the cloud, and an overview of deploying redundancy and failover

Auto-scaling in the cloud

Killer app of Clouds is being able to grow your site on demand; here's some popular ways to do it.

Future of clouds

Providers other than Amazon, DIY clouds, and more.

Goals

After this session you should have a good idea of the possibilities available to you when deploying Drupal in the cloud, and a good enough technical understanding to deploy a Drupal server in the cloud.

Resources

You can get a general understanding of cloud-based deployment with only a general understanding of the LAMP stack; to get the most out of this session you should be familiar with setting up Drupal on a fresh linux install using only the command line.

Overview

We'll discuss ways to develop reusable and flexible JavaScript components by leveraging JavaScript's full potential and using Drupal's lightweight JavaScript frameworks. We'll look at several JavaScript components and see how they were implemented and how they interact with each other.

Agenda

* The JavaScript widget skeleton
* Bootstrapping components with Drupal.behaviors
* Interaction with delegates
* Managing events
* Talking back home
* Making it themable and translatable

Goals

The session aims to create a better understanding of how JavaScript components can be built in a more modular and extensible way.

Resources

You should be familiar with JavaScript and jQuery.

Overview

Analysts estimate that 75% of attacks against web servers enter at the application, not the network level. And as many as 15% of these attacks are due to poor coding practices. With the help of well known security firms, We'll discuss ways to secure your Drupal application.

Agenda

* See For Yourself - demonstrations of application attacks
* Case Study: Secrets to Securing a Social Network
* Key Habits of Secure Drupal Coding
* Vulnerability Detection to Remediation
* Security Resources for Drupal Applications
* Discussions

Goals

You will learn best practices you can employ right now to build secure Drupal Application code that meets security compliance standards and maintain customer confidence.

Overview

Installing and maintaining a Drupal site is a relatively straight forward process, even if most of the work required has to be done manually. Which is entirely sufficient when you have a single site, or even a small number of sites.

But what happens when you have ten, a hundred or even a thousand sites? These simple tasks literally become the 'death of a thousand cuts'. You don't even need to have a hosting company to become overwhelmed by this situation, the simple fact is that manual interaction can only scale so far.

Aegir is a new set of contributed modules for Drupal that aims to solve this very common problem. it does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.

In Norse mythology, Aegir was the god of the oceans and if Drupal is a drop of water, Aegir is the deity of large bodies of water.

It is a complete rewrite of the Hostmaster system that has been running the Bryght hosted service for nearly four years, and has many years of research and development behind it.

The system was designed from the ground up by Adrian Rossouw (author of both PHPTemplate and the forms API) to be a first class Drupal citizen, allowing for integration into a wide variety of configurations, and has been sponsored by Raincity Studios, a well known face in the Drupal community, who acquired Bryght in 2008.

Agenda

* History - A system 5 years in the making.
* Goals - Guiding principles in the development of Aegir.
* Installation walkthrough - We show you how to install the system.
* User walkthrough - We show you what you can do with the system once installed.
* Under the hood - An overview of the system's architecture.
* Status - What's ready today? Can I start using it NOW?
* Roadmap - Where to from here? Extendability.
* Integration - Ecommerce, White boxing and more.
* Discussion - Questions and possible future features.

Goals

This session will help you understand the Aegir system, how the different pieces fit together and how it can help you or your business save time and money on tasks that are easily automated.

Work smarter, not harder.

Resources
* Ægir workgroup
* Overview
* Goals
* Design and terminology
* Roadmap
* Installation wizard slide show
* User tour slideshow

Overview

Drupal needs media handling, but more than that, Drupal needs a way to handle ''Social Media''. YouTube or Flikr are excellent examples of gallery-style media sites that have experienced organic community growth (Flikr more than YouTube). Facebook has fairly robust handling of photos and leverages their "social map" to deliver an exciting experience.

Drupal is already an excellent platform for building robust social networking sites and community collaboration spaces. Media handling is rapidly improving. With the current discussion on how to formalize media handling in Drupal and the continued development in the social networking space, Drupal is a natural choice for developing social media projects. All that is missing is a straightforward implementation path. The Scald platform -- first developed for a groundbreaking new project from Chicago Public Radio -- is a first step down that path.

Agenda

• What is "Social Media"?
• How "social" and "media" are currently accomplished in Drupal
• The argument for a new framework
• Scald architecture highlights
• Brief demo (Vocalo.org)
• Current Status
• Future plans & how you can help

Goals

Attendees should leave feeling that they have a grasp of how Drupal currently stacks up in the Social Media space. They should understand the basic Scald feature set, its architecture (on a high level), the rationale behind its development and some ways that Scald can be used as an effective tool in developing social media websites.

Resources

• Social Media on Wikipedia
• Vocalo.org
• Scald module page

I want to open a discussion on how to use various components and sides of Drupal to enable us, Developers to improve usability in our projects. Le us discuss how to use Form Elements, Helper Libraries, Naming conventions and Insert Your Birght Idea Here to enable the community to improve Drupal's usability.

Overview
Improving usability for project Foo might make the same software horrible to use in project Bar. That is why we could look at improving usability in Drupal by not making Drupal core more usable. But by enabling the developers to make Their Drupal project more usable for Their users in Their specific cases: enabling the community to improve usability.

Looking at Drupal as a Framework (the CMF) gives us opportunities: We can improve usability by enabling Dan the Distro Builder to put together a Blog Install Profile that is very usable for Bob the Blogger.

Agenda
* Introduction on Usability in general: Why is it so hard to get right in Drupal?
* Short introduction on why this 'enable' route might work better then the oldfashioned 'make Drupal core more usable'.
* Open Discussion on ways to achieve this.
* Putting Money where Mouth is: create code, docs and projects after the outcome of the discussions. This should be the biggest part: we must avoid this becoming a vapourware project and start off with some Real Working Code and Good Resources.

Goals
Setting up and initial infrastructure that will help people who want to contribute to the usability of Drupal.
Get a message out about this initiative and to enthuse developers for this usability project.
And, in the very end: to allow you to build a perfect site for your specific users.

Resources
Please collect any nice code (form elements) nice ideas (the back of a beermat) or good designs (like That One CSS Trick to align forms) on your laptops or servers. So that we have some real working code and ideas to start off with.

Overview

Online Presentation Slides

Accessibility should not be considered an option or an add-on. It is the responsibility of the entire team, from the designer, to the coder, to the writer, to the themer, and even to the business development team.

Agenda

1. Accessibility Guidelines & Drupal
   • WCAG
   • PAS 78
   • Section 508
2. Themes & Accessibility
   • HTML
   • CSS
   • JavaScript
3. Modules & Accessibility
   • For administrators
   • For end users

Goals

Fortunately, Drupal has a solid foundation for coding standards and separating its data, logic, and presentation separate from each other. This has greatly contributed to the ease in which to make a Drupal site accessible. But is it enough and could it be better?

Resources

• WCAG
• WCAG 1.0
• WCAG 2.0
• PAS 78
• Section 508
• Drupal Accessibility Group

Link to the slide:
http://quiddities.com/presentations/2008/08/drupalcon-accessibility/

Overview

The panel will discuss their experiences producing the last several Drupalcon conferences (Boston, Szeged).

Topics include

* Effort level description
* Budgeting
* Venue selection & infrastructure logistics
* Attendee travel logistics
* Event website; registrations / commerce
* Session proposal management
* And other topics

Resources

The presenters will likely need a projector for showing PPT/Keynote presentations.