I'm beginning to fall into the group of people that loathes their laptop and thinks that the standard website just lacks personality, depth and an ability to do anything useful. Of course facebook, youtube, tudou, etc. may prove me wrong.

Isn't there anything more? What if I don't have time to go to a website but I still want the data?

Services API to the rescue. You've created an awesome website now get your data off of the site (or onto the site) and to your users' phone(s), twitter account, dashboard widgets, other websites, or ??? (anywhere that is not your website). in short... extend your reach.

Services API provides a nice simple way to create an API for your site just like the flickr API, Twitter API, basecamp API, etc. etc. Services currently allows for XML-RPC, JSON, REST, SOAP and AMF (Flash/Flex) API calls (read and write). API-Keys, quick hooks/calls and loads of sample code to get your site's API up and running quickly.

yyuummm...

A brief case study on how we have built an online test of spoken English using Drupal + Flash + Webcams.

Topics covered:
- Why we used Drupal
- Flash <-> Drupal data exchange
- Flash Media Server and bandwidth considerations
- Demonstration of test

I will review the business case for using Drupal vs rolling your own code, using our experience rewriting the fourth version of one of our main applications using Drupal.

Topics covered:
- Things you will (likely) need when building a big project
- Things Drupal + community can provide
- Things Drupal does not provide
- Contributing back to Drupal

Anyone else who has something to share about the financial / business benefits of using Drupal is welcome to join in.

We will see what is internationalization, localization and how Drupal implement these concepts while building a completely multilingual website.

You found a module and its great but it doesn't do this one little thing that you need for your project. No problem you say, I'll just take the code, modify it, and then your all set.

but now what?

What are the next steps?

Lets talk about how we collaborate on Drupal, custom modules, and our projects.

Is the issue tracker and patches all we can do? Is there more?