Developer

In this BoF we would like to exchange ideas and experiences in several different areas, including:

• Current situation of Drupal Community in Austria

• Increase public awareness regarding Drupal in Austria and regarding potentials of Drupal Community in Austria in particular

Scrum is a very useful framework to help you stay in control of Drupal projects. But you need to know its limitations and also customise it appropreately to suit your projects.

The main aim of this BoF is to discuss and exchange practical information on the use of Scrum in real projects and therefore no presentation is planned.

As a follow-up to the Drupal: TNG session, let's keep the conversation going. What should the context API look like? What other use cases for plugins can we find? What happens to hook_menu? Let's look into these questions and figure out the next steps (after we finish Drupal 7!).

Please be sure to read up on the conversation to date first: http://groups.drupal.org/butler

• How to use Varnish with Drupal
• Writing good VCLs
• Using ESI, and serving micro-content (individual blocks, panes...)
• Delivering micro-content via ESI with minimum bootstrap overhead
• Other approaches to block-delivery via ESI (memcache, using David Straus' experimental kargo-event handlers, ???)

And any other ideas!

The ESI module (http://drupal.org/project/esi) will be released shortly, so there should be code to play with too.

As an open source platform and content management system (CMS) for building dynamic web sites, Drupal is establishing itself as a leader among social software solutions for governmental, intergovernmental, and nongovernmental organizations. Having already gained a small but significant share of the domestic and worldwide public sector CMS market, the solution appears on-track for continued growth.

From the panel description:

Working with Drupal brings the power of its community to work for you. But it also involves you in that community in ways that you might not expect. We'll cover some of the hidden costs of bringing Drupal into your organization, plus the resources you will need in order to keep your project sustainable.

This will feature lively panel discussion covering best practices for Drupal contributions maintainers and the rights and responsibilities of Drupal users.

Topics that we will cover:

• What are the rights and responsibilities of Open-Source developers?

The Pay module provides online payment handling in Drupal. Sometimes you need a simple way to receive payments from your Drupal site without the complexity of a shopping cart. Pay provides the ability to add a payment form to your site -- or to a specific piece of content on your site -- and enable a single-click payment transaction. No cart, no check-out necessary.

Pay does the heavy-lifting of transactions:

<

ul>

One of the main topics at the Core Developers Summit on Sunday in Copenhagen was how do we lessen the barrier to entry for contributing to Drupal, specifically code. With the git migration, we have a good opportunity to refine this process and we have decided on how to help the process, but we are still in great need for experienced Drupallers to review CVS/Git applications.

Current discussion: http://groups.drupal.org/node/88599