This is a small informal presentation of the guitar module (http://drupal.org/project/guitar) which lets you put guitar chord diagrams on your website.
Depending on the interest, we can go through how to use the module, how it works, potential use cases and planned features.
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
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.
This BOF is for brainstorming and discussing the use and relevance in Drupal.
A discussion about the findings of the two formal usability tests conducted on Drupal, possible resolutions, and methods for building usable applications.
* Recap of the top usability issues
* The Drupal Audience - Persona's defined
* Possible Resolutions
* low hanging fruit (easy, impactful fixes)
* high hanging fruit (harder, but important fixes)
* Methods for user centered checks and balances
The goal of this BoF is to discuss the usability findings and offer up solutions that will make Drupal more usable for new and seasoned users. We'll present ideas, talk about our audience via personas, and highlight methods for achieving more usable results in the future.
No required resources. Although it would be helpful to familiarize yourself with the two usability studies, which can be found on drupal.org (http://buytaert.net/tag/usability)
Since the drupal world is constantly growing with more and more (non-)commercially oriented projects and people starting off, I thought it was time to come up with a platform that tries to connect projects (as well as staffing requests), people (drupalists) and knowledge. As of now I am in the final stage of launching this non-commercial platform, called drupaleo, as a beta version.
clear mind required
A community effort to help a NGO get some ass-kicking internet presence
On the first weekend of October 2008, in only 2 days, the Drupal French Community will build a complete and live website for a selected NGO. All free. Free as in free beer, and free as in free speech.
A lot of the organizational details have been ironed out.
Though we have discussed a lot the question of "how the hell do we pull this off?" and have a detailed an action plan... there must be a million things we forgot.
Who should come?
So we are calling on all that have experience in organizing Codesprints/ Hackathons/ Mashpits and generally community events to join us and share their experience and thoughts.
What should come out of the session?
We would really like to hace constructive criticisms on our plan to adjust and augment it so we can put all the chances on our side to pull off this event.
The rules modules allows site administrators to define conditionally executed actions based on occurring events (ECA-rules). It's a replacement with more features for the trigger module in core and the successor of the workflow-ng module.
It opens new opportunities for site builders to extend the site in ways not possible before.
* Module overview - What is it and why do I need it?
* Usage example: Build a simple workflow with rules and CCK.
* Advanced features: Rule Sets and scheduling
* How modules can use the rules API to extend it.
* Comparison to the trigger module and drupal actions
By the end of this session attendees will be familiar with the capabilities of the rules module and will know how to make use of it to speed up site development.
Module developers will know how easily their modules can be extended and how to obtain better code reusage by developing with rules.
You should be familiar with popular drupal modules like CCK and Views. Coding skills are not required but beneficial for a better understanding of the short part about the API.
I want to open a discussion on how to use various components and sides of Drupal to enable us, Developers to improve usability in our projects. Le us discuss how to use Form Elements, Helper Libraries, Naming conventions and Insert Your Birght Idea Here to enable the community to improve Drupal's usability.
Improving usability for project Foo might make the same software horrible to use in project Bar. That is why we could look at improving usability in Drupal by not making Drupal core more usable. But by enabling the developers to make Their Drupal project more usable for Their users in Their specific cases: enabling the community to improve usability.
Looking at Drupal as a Framework (the CMF) gives us opportunities: We can improve usability by enabling Dan the Distro Builder to put together a Blog Install Profile that is very usable for Bob the Blogger.
* Introduction on Usability in general: Why is it so hard to get right in Drupal?
* Short introduction on why this 'enable' route might work better then the oldfashioned 'make Drupal core more usable'.
* Open Discussion on ways to achieve this.
* Putting Money where Mouth is: create code, docs and projects after the outcome of the discussions. This should be the biggest part: we must avoid this becoming a vapourware project and start off with some Real Working Code and Good Resources.
Setting up and initial infrastructure that will help people who want to contribute to the usability of Drupal.
Get a message out about this initiative and to enthuse developers for this usability project.
And, in the very end: to allow you to build a perfect site for your specific users.
Please collect any nice code (form elements) nice ideas (the back of a beermat) or good designs (like That One CSS Trick to align forms) on your laptops or servers. So that we have some real working code and ideas to start off with.