Drupal Lightning Talks
Tags:
CMS: Drupal
Friday - 9:00am - Friday - 10:00am
Description:
Have a great new module you want to show off? Know some tips and tricks that you'd like to share with the community? Want to read from your epic poem, "Druplicon's Progress?"
Then the Drupal Lightning Talks are for you!
What is a Lightning Talk?
A lightning talk is a 5 minute (or less) presentation on a topic you'd like to share with the community. The Perl community has been holding lightning talks for years, and the PHP community has started following suit.
Lightning talks tend to be direct, to the point, and light on the details. They're appetizers to pique our interests, not full course meals.
With a strict time limit of 5 minutes, we should be able to hold 11 talks during this one hour session. If the demand his high enough, we'll expand the session to 2 hours, and hold 20 talks.
How do I sign up?
Comment on this session with a title like: "LT: My great module...". Give a brief description your presentation (a good opportunity to practice your brevity). Make sure your contact tab is turned on (as we'll be contacting you to confirm your talk before DrupalCon).
What should I present?
Any subject is great - as long as you're interested in it. Lightning talks are a great opportunity to point the spot light on a topic that might not require a session of it's own.
If you're still struggling for ideas, here's a list of suggestions from the Perl community, and here is a more detailed write up on Giving Lightning Talks.
We look forward to seeing your talk!
Lead by:
- Login to post comments
I will attempt to break and unbreak your brain in 5 minutes with viewfield (a CCK field that places views inside of nodes).
A super-fast tour of Token module, a centralized API for token/value replacement tasks in Drupal. Want to send out parameterized email? Want to provide a simple templating system for your module's output? Token makes it easy.
I'd like to present an idea for a pair of modules that will better integrate discussion with other content types. A Pivots module would let users navigate from nodes to related conversation. Unlike the way comments are treated, a message could be related to more than one node. A Trackers module would let users subscribe to Pivots, so that they could track ongoing conversation.
(I can't register for the site right now, so I'm including a link to my homepage below.)
Paul Resnick
Why long-life PHP session cookies are a bad idea and why a "Remember me" login option, provided by the Persistent Login module, can be both more secure and more convenient for users.
In 5 minutes, what Drupal actions are, the future of the actions module, and how to write actions for your module. Really - in five minutes.
Quick talk about the new developer module, what it can do today, and what it could do tomorrow...
Brief overview of the current capabilities and future direction of the Asterisk PBX integration module.
An overview of the state of the MySite module and the roadmap for new features for user-customizable homepages inside a Drupal site.
http://drupal.org/project/mysite.
--
Ken Rickard
http://savannahnow.com/user/2
http://ken.blufftontoday.com/
http://ken.therickards.com
was me, by the way.
Pando Networks uses Drupal extensively. We use it to run our various web sites (www.pando.com, developers.pando.com, rss.pando.com), and have added Pando as a media type, allowing people to contribute Pando packages into Drupal sites, subscribe using Pando RSS, etc.
My attempt to provide Drupal with a data model and incremental database propagation.
Overview of a deletion API for Drupal core could significantly improve the flexibility and data integrity of the deletion process.
The project.module is the central tool that powers all Drupal development (both core and contrib) on drupal.org. Everything from issue tracking, to revision control integration, to the release system, is handled by these modules. Unfortuantely, only a tiny subset of the Drupal community (mostly a single volunteer, me) actually maintains any of this code. With the huge user base, just managing the issue queue can be an overwhelming task, much less having time to fix the bugs, which leaves even less time for new features to improve the development workflow. Contrary to popular belief, you don't have to be a mega-uber-hacker-wiz who can grok all the "scary code" to participate. Find out some of the ways you can help support and enhance the tools that make Drupal development tick.
in case it wasn't obvious, that was written by me. silly site letting us post anonymous comments... ;)