A short meeting to prepare for the road map of the French Drupal Community post Convention
* Training, Training, Training !
* DrupalCon Paris ???!!!
* Association, no Association?
* Newsleter to the whole of the community
* Schedule work on Drupal'n'GO
The same way Google has summer of code, this idea is to have something like Google year of code.
We're talking about a website where the community can collectively fund projects (ie bounties), design them collectively and fund them collectively.
This session is to hear your thoughts and ideas about the matter.
* FOSS Factory, an introduction
* Does the community need this model
* If so, what's the idea way of using it (ie implemented within the drupal website or left as an external site)
* what kind of problems would be posted on it, what level of expertise would be required to solve them.
Basically I would like to know if this idea makes sense at all, and if it does, I would like to know how to make it happen.
please see www.fossfactory.org
Extra BoF Spot for the Usability Sprint
Group working on the Node Forms
Building a website for Drupalcon.org is a challenging matter. There are lots of features to work with, the site should adapt to the needs at any time and of course should show that when Drupal is used to build its own conference website, it should do cool stuff for its attendees and other interested parties.
There were lots of design decisions made on the site given the needs we specified based on our look at previous Drupalcons and our own expectations. Sometimes existing modules fit well into our plans, quite a few times we needed glue code or our own code to do the work. Sometimes our own code resulted in superb end results but then also sometimes made mistakes. It also turned out that some of our design choices were not perfect and in some cases our implementation was not adaptive as we wished.
I hope to tell stories about these experience, dive into some details about the implementation, glue code, own code. You will most probably not get clear recipes, and definitely not ready to use code.
Ps. (If we have time and interest, we can get into the making of do.drupaltown.org - our management website for this event and lessons we learned using and sometimes not using that).
Semantic web is a popular buzzword in Web industry today. Some even call it Web 3.0. There are a number of different ways to extract meaning from content. Some of them will be discussed with a more detailed case study of Zemanta, a tool for automatic suggestions for content while it's being created.
* Short overview of semantic web
* Tools and API's
* Zemanta, UI decisions and things to think about
The goal of this session is to learn a few things about current state of startups in this field and to see how one of them did integration into Drupal.
CiviCRM is a constituent relationship management system that integrates with Drupal.
That's the simple version of the story.
Now here's what was overheard at Port Royal last night: 'Dude -- do you not realize the ground you're walking on is littered with corpses?'
Don't let the next lot of corpses include yours.
If you're working (fighting) with CiviCRM now, if you've worked with it in the past, or you know that you'll be needing to use it in the future, come along and we'll share experiences, tips, and code.
There is already a session about Facebook Application development. The session is scheduled for 11am on the 28th. At that time I'll talk about what a Facebook App is and tools for building them on Drupal.
This BoF will be a chance to work with the modules and ask questions specific to your own site. Perhaps even get your site running on Facebook, if you have not tried to do so already.
I'll be there to answer questions and help troubleshoot. So this is a good chance to get started if you haven't worked with Facebook before. And a good chance to ask questions if your stuck on any particular feature.
If you want to contribute to the Drupal for Facebook project, we can talk about the best ways to do that.
This talk gives an introduction to Bazaar (bzr) - the distributed source code revision control system developed by Canonical Inc.
In this session, Lenz will provide an overview about the general concepts of distributed source code revision control and how Bazaar (bzr) fits into this picture. The bzr terminology and most useful commands will be explained as well as examples on topics like:
Attendees will have a better understanding on how distributed revision control works in principle and how it can be utilized with Bazaar. The basic commands needed to get going will be covered, so users can get familiar with the concept by themselves.
Some basic understanding of source code revision control systems (e.g. CVS, Subversion) is probably required to make the most out of this session and to understand why Bazaar (or any other distributed revision control system) is superior to these.
A "Cloud" offers a virtualized datacenter infrastructure that allows you to build your own network applications. In this session, we'll cover an approach to implementing Drupal in the cloud using the popular Amazon Web Services as the cloud service.
After this session you should have a good idea of the possibilities available to you when deploying Drupal in the cloud, and a good enough technical understanding to deploy a Drupal server in the cloud.
You can get a general understanding of cloud-based deployment with only a general understanding of the LAMP stack; to get the most out of this session you should be familiar with setting up Drupal on a fresh linux install using only the command line.