Intermediate

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

In his Drupalcon keynote yesterday, Dries noted once again the necessity of increasing the number of skilled Drupal practitioners to sustain the Drupal project's trajectory. The Drupal conference itself, it has been pointed out, mainly attracts the (aging) faithful. Encouraging new talent and growing the skills of the newly interested is really the challenge. We should be taking this challenge on as our job.

Some of us do and have built a business model around the idea of sustaining an evolving Drupal ecosystem via a variety of training, collaboration and community organizing techniques.

Drupal has now at least two community products usable out of the box. http://commons.acquia.com & http://openatrium.com
+ http://drupal.org/project/voicebox targeting targets community media (that should go out shortly)
+ facebook like feature http://sndemo.dev3.webenabled.net/node/1

There is a need to see how those projects compare and are able to "compete" with non-Drupal products.

The output of this brainstorming session could be a list of features based on a competition analysis focused on the most successful of each targeted audience :

This is a talk a the future developments in Solr some of these include
- Apache Solr Multiserver (formerly multicore)
- Apache Solr field collapsing (experimental I know but I am about to use it with a client)
- Apache Solr Geo local
- Apache Solr Views
- RDF the use of tuples in search/ Solr Sparql interface

But everyone bring along your thinking caps about how we can structure this better in the future and how this hooks into some of the new thinking about generic search api's

Are you sick of hearing "Drupal is ugly"? Are you devoted to change that and make Drupal sites look awesome? Join the gang of Drupal designers and start sharing and promoting your designs, write blog posts and making the Drupal side of Internet prettier.

Come and discuss the future, purpose and features of Drupaldesigners.org website, join the Beta testers, participate in the process of creating the Drupal designers community.

There are several newer Drupal projects and vendors in Norway. Maybe those who are at DrupalCon in Copenhagen could get together and get to know each other? Come with your curiousity, questions and topics to talk about. Some topics could be:

• Drupal and the two/three written languages in the populationwise small country
• Could or should we organize a Drupal BarCamp or meetup, and where?
• General networking for support and commerce. Or something like that, less cheesy.

Most people think of famine, war, disease, hopelessness and big bucketloads of sand when Africa is mentioned. That's a shame really because Africa is, in many respects, a continent on the move.

In this BOF we look at the current state of Drupal in Africa: pitfalls and possibilities. What is happing today, what is happening tomorrow and where can you fit in? Topics include geodata, local caching, capacity building, mobile app development and education.

Meet and discuss London 2011. If you are interested in helping move the London 2011 DrupalCon forward, then come along and meet everyone else.

This is a chance to meet in person if you are already helping, and a chance to find out what is going on, and to get involved if you are not already helping.