Site architect

Overview

This session will be presented by the maintainers of the Location and GMaps modules. Updated, stable versions of these modules will be released this summer, and we will talk specifically about the capabilities of these modules. We will also address the roadmap for growing these modules into a broader GIS/mapping platform for Drupal.

Agenda

• GMap and Location updates--stability, new features, api features
• current GIS/Mapping capabilities with GMap and Location--what we can do with Drupal right now
• GIS/mapping platform goals--what we want to be able to do with Drupal
• technical roadmap--a clear technical plan to meet those goals

Goals

The goal of this session is to engage people with the current evolution of Drupal mapping by sharing what is currently possible, and to get community buy-in on Drupal as a GIS/mapping platform by presenting a clear set of goals for the near future.

Resources

The State of Geospatial in Drupal:
http://groups.drupal.org/node/12485

Drupal mapping group:
http://groups.drupal.org/mapping

Location module:
http://drupal.org/project/location

GMap module:
http://drupal.org/project/gmap

Geo module:
http://drupal.org/project/geo

OpenLayers module:
http://drupal.org/project/openlayers

Overview:

Imagefield Gallery is a module that's been around since shortly before Drupalcon Boston. I created it with the intent of making gallery management for an existing site easy for single nodes. Since that time others have used it for their own sites, and have extended it to work with proprietary gallery types that have not been contributed back. I would like very much to introduce the drupal community at large to imagefield gallery and encourage them to help develop it in a direction that could be beneficial for ALL of drupal, not just a small subset.

As stated above, imagefield gallery's primary purpose is to create galleries on a node from an existing imagefield. The new 2.x version cleans up the admin, and is striving to squash some old bugs, and add new features. In development is the ability to do node references, as well as a new gallery type. Imagefield Gallery makes creating new gallery types pretty easy and straight-forward. These gallery types are re-usable in a large number of instances and allow the site administrator to customize gallery types per content type.

Agenda

• Current Capabilities
• What I'd like to see donated by the community
• What about D6?
• What could the future hold?

Goals

Ultimately the objective of this session is to introduce Drupal at large to the Imagefield Gallery module, and show them what it can do for them. With some help I believe imagefield gallery can fill a significant void in the current Drupal codescape and give Drupal a varied and significant gallery system upon which to draw.

Resources

Project Page:
http://drupal.org/project/imagefield_gallery

Development/News Blog:
http://www.worxco.com/blog-categories/imagefieldgallery

Overview

The Drupal 6 menu system has a fundamentally different architecture from what was present in Drupal 5. This session is designed to highlight the key features of the new system, and give some code-level examples of how to use them well and what to avoid.

Agenda

* How does Drupal 6 serve paths and render links
* When are the menu hooks called
* When to define a router item
* Examples of bad code
* Examples of good code
* Advanced tricks and tips

Goals

By the end of this session I hope you will have thrown off the shackles of your Drupal-5-based thinking about the menu system and be ready to use the features and be aware of the limitations of the Drupal 6 menu system.

Resources

You should be familiar with writing a hook_menu implementation and preferably the {menu_router} and {menu_links} tables to get the most of this session

Making a Digg/Reddit/Propeller clone with drupal

Today user submitted story sites are very popular.some examples are digg/reddit/propeller etc.In this session i am going to show how to create such site with using drupal and available modules.

Agenda

* Architecure of social site.
* How to use drupal?
* Available modules.
* Customization of modules to achieve the needed functionality.

Goals

In the end attendee will have knowledge on drupal and its module which a user can use to build such sites and can create their own.

Resources

none.

Overview

This session will show off the results of Drupal's Google Summer of Code 2008 projects. Students who make it to Drupalcon will be demoing their own projects, and we'll also show off projects from the students who can't be there.

Agenda
The following projects will be shown during the course of the session, as time permits.

• Apache Solr Improvements
• New Aggregator for Drupal core
• Bookings API
• Charts module Views integration
• Color module improvements
• Document Import Module
• Embed Widgets
• Revamped Help system
• Icon module
• Image manipulation GUI
• Memetracker
• New nodequeue sub-modules
• OAuth/Services module integration
• Open ID Attribute Exchange
• PluginManager
• Core search improvements
• Security scanner
• Usability Suite
• Validation API
• Version Control API / Project module integration
• Views datasources

Goals

This session will allow Summer of Code students to show off their hard work, and for the Drupal community to get a first-hand look at all the cool stuff that was produced over the summer. Summer of Code students typically make excellent employees as well, for those looking to hire. ;)

---

NOTE TO ORGANIZERS: I put down "90 minutes" because that'd be a much more comfortable time frame during which to show off 21 projects. But every other year we've managed to do it in 60, so if 90 minute slots are short, you can push the time allotment back.

This will just be an informal gathering of the women who make it to Drupalcon: the Drupalchix (also known as the "7% club" ;)).

We did this in Barcelona and Boston, and it was awesome. :D

Topics might include things like:
* What are our various backgrounds/experiences prior to coming to Drupal?
* What is it that we’re currently working on?
* What have our experiences in the community been like?
* What can we do to encourage more women in open source/Drupal specifically?

Overview

Adding a Display Name in the core of Drupal has been a hotly debated topic for at least the last 4 years. The addition of a Display Name impacts on many areas within the project. With Drupal 7 it seems the right time to put this much need feature in core. The only questions are how and who.

We need a face to face discussion to define a clear set of requirements that will feed into the code sprint on the August 31 to result in a Drupal 7 patch commit.

Agenda

• The history of the issue (see Resources below for material to read beforehand).
• The sticking points and how they can be overcome...
  • The non-uniqueness issue.
  • The auto-complete and search results issue.
  • The security issue.
• Defining a clear set of requirements and points of action.
• Who will in build the Drupal 7 patch in the code sprint.

Goals

A Display Name field and associated admin and user interfaces in core in Drupal 7.

Resources

Please ensure you are familiar with:

• The issue thread for Add a Display Name field to core in addition to Username
• The wiki page for Add a Display Name field to core in addition to Username

or How To Build a Stock Exchange in Three Months With Zero Knowledge, 9,000 Euros, and a Big Supply of Slovak Beer, errrr, Motivation.

Fusu is the Domain Stock Exchange that allows domainers to trade derivative interests in premium, high value domains. At launch, the value of domains on the Exchange exceeded $1.5 million USD. The initial prototype was built in three months by three developers that had basically zero knowledge of Drupal.

Agenda

* From zero to hero - prototype in 3 months
- Drupal as RAD framework
- Drupal as framework
- Closed beta with invites made easy
* Overview of a complex system:
Custom modules: financial backend, accounting, auctions, notifications, graphs, management
Modules used: invite (get users), affiliates (get paying users), dhtmlmenu (oh), cronplus (why not core?), buddylist (everything is social), cacheclear (ah the pain with cache), glossary (nice), faq (also nice), casetracker (for bugs)
* Challenges and lessons learned:
Deployment and development cycles
Scalability
Core hacking
Module hacking
Menu and caching
Drupal 6.x

Goals

We present how we built a relatively complex application in Drupal, describe the challenges we faced or are still struggling with. The goal is to show to the audience that using Drupal can be an efficient solution to create applications and not just content sites.