This site is archived.

45 minutes

How to get a themer to call you the morning after.

mortendk's picture
Submitted by mortendk on Tue, 08/05/2008 - 11:45.

It can be hard to look up from the daily work and se whats going on at the other side of the fence.

This will be a talk where themers can express their wishes for module developers and how it could be in ideal world, and vice versa
to give both parts a good understanding of the challenges that lies ahead in the day to day work.

It will be a round talk so come join and lets share our knowledge of both worlds

* what makes a crappy module for a themer
* what makes a really cool module for a themer
* basic knowledge - what coders can expect a themer / designer knows - is it enough or?
* day to day problems in the theming world
* day to day problems in the coding world
* what "documentation" -cant you just read the code? its in line 1208

* come all together now... a even better tomorrow ;)

The goal of this session is to give module developers and theming-css geeks a better understanding of each others world.

some experience as a themer / module developer

Indexes and denormalization: keys to scaling sites with massive content

David Strauss's picture
Submitted by David Strauss on Wed, 07/30/2008 - 22:35.

Session recording

Session time: 
08/27/2008 - 16:00 - 08/27/2008 - 16:45


Relational databases store, index, and retrieve data using using predictable patterns. Indexing data well -- but not excessively -- requires understanding indexing overhead and usage by query execution planners.

But, even the perfect indexing plan layered on top of existing tables cannot satisfy all needs: relational databases have significant limitations for indexing data. Particularly, they cannot index data across multiple tables. While Oracle and Microsoft SQL Server provide some in-built tools (materialized views and indexed views) for alleviating this limitation, users of open-source databases like MySQL and PostgreSQL must consolidate and preprocess data to scale popular services.

The Denormalization API streamlines the process of consolidating node data into tables structured for radical scalability.


* How is Drupal data stored?
* Overview of indexing tables
* Index data structures
* Query execution plans and indexes
* What is denormalization, and why is it necessary?
* Typical hurdles for implementing denormalization
* Using the Denormalization API


Attendees should leave with an understanding of the benefits and caveats of indexing and denormalizing data. And, if they choose to denormalize, how the Denormalization API can streamline the work.


Attendees should be familiar with Drupal's node system, SQL, and basic database administration.

Patching core for performance

David Strauss's picture
Submitted by David Strauss on Wed, 07/30/2008 - 22:21.


The stock Drupal core has a number of bottlenecks and limitations for high-traffic and enterprise deployment. Many of the top Drupal sites maintain internal, patched versions of Drupal. While each of these internal versions is custom-built, the patches applied and techniques used to maintain the patches are consistent across these sites.


* Popular patches used by high-traffic sites
* When these patches will be in core (or why they're not in core)
* Patch conflicts to watch for
* Deployment strategies to eliminate or minimize downtime caused by necessary changes to support the patch changes
* How to use version control systems to efficiently maintain a patched core without falling behind when the standard core applies security and bug patches. The demonstration will be using bazaar-ng (bzr).
* Other community resources for making this work easier
* Case studies in patching core for performance

Patches/modules considered

* Master/slave replication
* memcached
* Cache Router
* Removing LOWER()
* Database lock removal
* Possibly others


Attendees should leave with the following capabilities:
* How to decide whether patching core is worth the trouble
* How to maintain a patched core


Attendees should be familiar with applying patches and using version control systems.

Google and Open Source, with Highlights from GSoC and GHOP

lh's picture
Submitted by lh on Wed, 07/30/2008 - 19:36.

Session recording

Session time: 
08/28/2008 - 15:00 - 08/28/2008 - 15:45


Leslie Hawthorn from Google will be coming to Drupalcon to talk to us about various open source stuff.

In this talk, Leslie will explore the past, present and future of the Google Summer of Code program, with an emphasis on Drupal projects. She will also cover the genesis and results of the Google Highly Open Participation Contest and future plans for this initiative. She will also briefly cover Google's use of Open Source software, the role of Google's Open Source Programs Office and how & why Google supports Open Source.

Leslie does not speak Magyar, but will definitely make up for her lack of domain expertise there with amusing anecdotes and, possibly, shadow puppets.

Drupal'n'Go / Drupal For Good Code Sprint

Ori Pekelman's picture
Submitted by Ori Pekelman on Wed, 07/30/2008 - 12:42.

A community effort to help a NGO get some ass-kicking internet presence

On the first weekend of October 2008, in only 2 days, the Drupal French Community will build a complete and live website for a selected NGO. All free. Free as in free beer, and free as in free speech.

A lot of the organizational details have been ironed out.

Though we have discussed a lot the question of "how the hell do we pull this off?" and have a detailed an action plan... there must be a million things we forgot.

Who should come?

So we are calling on all that have experience in organizing Codesprints/ Hackathons/ Mashpits and generally community events to join us and share their experience and thoughts.

What should come out of the session?

We would really like to hace constructive criticisms on our plan to adjust and augment it so we can put all the chances on our side to pull off this event.

Drupal and the Semantic Web: the Neologism project

scor's picture
Submitted by scor on Tue, 07/29/2008 - 17:56.

Session recording

Session time: 
08/30/2008 - 15:00 - 08/30/2008 - 15:45


The Drupal community is jumping in the Semantic Web bandwagon. Semantic Web Applications built with Drupal are starting to emerge from the different use cases of the community.

The Neologism project is one of the applications that benefits from the power of Drupal, but also constitutes a building block for the Semantic Web.

Neologism is a lightweight web-based vocabulary editor and publishing tool built with Drupal. It makes vocabulary authoring easy and fun. Just create a vocabulary, add classes and properties to it, and your vocabulary is instantly published and available online! Several formats are supported via content negotiation: HTML, RDF/XML and N3. All the term URIs are dereferenceable and point to their human readable description.

Some other Semantic Web projects could also be presented in this BoF.


* What is the Semantic Web
* Neologism use case: how Drupal helped us
* Why a Vocabulary editor?
* Other Semantic Web projects built with Drupal
* The future of the Semantic Web and Drupal

Rules - new opportunities for site builders!

fago's picture
Submitted by fago on Tue, 07/29/2008 - 11:23.

Session recording

Session time: 
08/27/2008 - 15:00 - 08/27/2008 - 15:45


The rules modules allows site administrators to define conditionally executed actions based on occurring events (ECA-rules). It's a replacement with more features for the trigger module in core and the successor of the workflow-ng module.

It opens new opportunities for site builders to extend the site in ways not possible before.


* Module overview - What is it and why do I need it?
* Usage example: Build a simple workflow with rules and CCK.
* Advanced features: Rule Sets and scheduling
* How modules can use the rules API to extend it.
* Comparison to the trigger module and drupal actions
* Outlook


By the end of this session attendees will be familiar with the capabilities of the rules module and will know how to make use of it to speed up site development.
Module developers will know how easily their modules can be extended and how to obtain better code reusage by developing with rules.

You should be familiar with popular drupal modules like CCK and Views. Coding skills are not required but beneficial for a better understanding of the short part about the API. A case study on Drupal with the YUI

v's picture
Submitted by v on Tue, 07/29/2008 - 09:59.


What is
12seconds lets you create and share short video updates with your friends and family.
Why Drupal for 12seconds?
Because it's a solid framework that just works well. Really.
What is the YUI?
The Yahoo User Interface (YUI) Library is a collection of JavaScript and CSS resources that make it easier to build richly interactive applications in web browsers.


  1. Using the YUI Grids
  2. Compressing the CSS
  3. ???
  4. Q & A


  • When building with the YUI it's important to know where to put it with all the other CSS files that Drupal spits out.
  • Attendees ought to walk away knowing how to use and customise the YUI Grids for their Drupal sites.



Introducing Memetracker

kylemathews's picture
Submitted by kylemathews on Tue, 07/29/2008 - 08:24.

Session recording

Session time: 
08/27/2008 - 16:00 - 08/27/2008 - 16:45


Memetracker is an exciting new module being written as part of Google Summer of Code. The module can be used to build news aggregator sites similar to Techmeme and Google News and also can serve as an excellent conversation tracker within online communities.


* What is a memetracker (define terms, show examples)?
* Why would I want a memetracker?
* Different ways memetracker can be deployed or how to integrate memetracker into a Drupal site
* Future direction for Memetracker


That session attendees understand what a memetracker is and when and where memetracker is appropriate to use. The session is intended for newcomers to the memetracking world.


Ideally, session attendees will have installed and used the memetracker module. Failing that, session attendees will have read the memetracker handbook page (yet to be written btw, but will before Drupalcon).

Front End Performance – How to make your website blazingly fast

kkaefer's picture
Submitted by kkaefer on Tue, 07/29/2008 - 00:29.

Session recording

Session time: 
08/28/2008 - 16:00 - 08/28/2008 - 16:45


This lecture-style session will present and discuss various approaches to improve front end performance. While server side performance has an impact on the speed websites are delivered, the vast par of loading time is spent on retrieving CSS, JavaScript and image files. For a truly zippy website, it is therefore vital to drastically lower the amount of time spent here. In his book “High performance websites”, Steve Souders discusses various ways to accomplish this. This session is based on that book but contains additional Drupal-related information and strategies.


* Anatomy of a web page
* Measuring the non-obvious and identifying bottlenecks
* The Hypertext transfer protocol
* Reducing HTTP requests
* Configuring Apache
* Additional optimizations
* Content delivery networks
* Related Drupal modules


You should get a feeling for what “front end performance” actually means and where the main problems are located. You will also learn how to tackle these issues in a structured manner, measure the effects and get to know the basics of the foundation technology of the web, the Hypertext transfer protocol.


You should be familiar with how a website is structured and know basic Apache configuration. Being familiar with HTTP is a bonus.