Birds of a feather (BoF) space

Fleshing out the plans is here: http://groups.drupal.org/node/12972

Looking for co-hosts!

example:
- do a card sort on the admin categories
- discuss the different 'dashboard' approaches people already use
- choose 2 options we want to compare / test

another example:
- let's pick a nice chunk of core interface text: labels, descriptions, help
- rework them for clarity, consistency and brevity.

BoF Usability Sprint Day 2

build prototypes: on paper, in photoshop and/or code
or: further work on interface copy, start documenting the copywriting guidelines we find.

BoF Usability Sprint Day 3

Test conceptcode with the Usability Testing Suite
Or work on concept some more, take it to the Code Sprint.
or: create patch for interface copy and start the guidelines handbook page on drupal.org

Fleshing out the plans is here: http://groups.drupal.org/node/12972

Looking for co-hosts!

example:
- do a card sort on the admin categories
- discuss the different 'dashboard' approaches people already use
- choose 2 options we want to compare / test

another example:
- let's pick a nice chunk of core interface text: labels, descriptions, help
- rework them for clarity, consistency and brevity.

BoF Usability Sprint Day 2

build prototypes: on paper, in photoshop and/or code
or: further work on interface copy, start documenting the copywriting guidelines we find.

Fleshing out the plans is here: http://groups.drupal.org/node/12972

BoF Usability Sprint Day 1

* zoom in on 1 or 2 issues we already decided upon before the conference
(redo admin categories, modules page, permissions page…)
* bring your ideas and proposals
* discuss the options, decide on 1 or 2 things we can work on.

example:
- do a card sort on the admin categories
- discuss the different 'dashboard' approaches people already use
- choose 2 options we want to compare / test

another example:
- let's pick a nice chunk of core interface text: labels, descriptions, help
- rework them for clarity, consistency and brevity.

Overview

Ubercart is well on its way to a Drupal 6 release (codenamed Uber Tuber). As of this posting, 26/32 modules have been migrated. However, these are quick API migrations without a lot of retooling that would drag out the update process. Uber Tuber will be similar in functionality to the 1.0 release, just compatible with Drupal 6 and sans a few external dependencies.

As was laid out in our development roadmap, we're planning further core improvements and Drupal 6 API updates for a 3.0 release. We have a good idea of what many of these improvements should be, but we want to do some serious brainstorming with other developers and themers with some planning toward actual implementation. We're excited about the new features Drupal 6 brings to the table and can't wait to fully embrace them in Ubercart.

As such, we invite anyone to attend who is interested in Ubercart on Drupal 6 or has knowledge of how the core changes from Drupal 5 to Drupal 6 might benefit Ubercart. We also aren't ashamed to admit that many of our core systems have proven less helpful for developers and themers than we initially imagined. As such, anyone who wants to see changes in the Ubercore should attend and provide feedback on how things can be easier.

Please see the "Optimization" paragraph related to Drupal 6 in the development roadmap for more information.

Agenda

* Update on the current status of Drupal 6 development.
* Discuss core Ubercart API improvements.
* Discuss theming improvements:
   - General core improvements
   - Updates for improvements in Drupal 6
   - Address invoice templates
   - Anything else?
* Discuss performance improvements:
   - Using 'file' for menu items
   - ... ?
* Discuss internationalization improvements:
   - Country/zone system overhaul
   - VAT!
* Discuss improvements in the contribution process.

Goals

Drupallers who attend this BoF will get up to speed on the state of Ubercart development in Drupal 6. Further, we'll be planning many improvements for Ubercart that will be worked into Ubercart 3.0 and recruiting as many people as possible to help in the work!

Resources

* Ubercart 2.x-dev - http://drupal.org/node/280820
* Development roadmap - http://www.ubercart.org/forum/development/5115/...
* Migration status - http://support.ubercart.org/discuss/67/...

Related sessions

Drupallers looking for a more general introduction to Ubercart should consider attending Introducing Ubercart instead. Most of the features will be the same for Ubercart 2.0, so that session should prove more helpful!

We'll also be performing A Hands On Guide to Module Development in which we will discuss the things we've done wrong and are starting to do right in module development. The session will include an example of developing a module that integrates with Ubercart.

* This session was posted as a BoF but could be turned into an actual session with enough interest. We would keep the tone informal, but could reach a broader audience with the larger space if necessary.

Overview

Lets brainstorm about what improvements we can make to the node access control system.

Agenda

* How to make it easier to grok
* What features should be there but aren't

Goals

Close with a sentence or two describing the outcome you'd like from this session. For example, is the goal to define a problem and come up with a solution? If you're imparting knowledge, what sort of knowledge should attendees hope to gain by the end?

Resources

Please read node_access() and all the functions it calls. Also be familiar with node_db_rewrite_sql(). If you have written a node access module, you are very encouraged to attend.

Overview

Although MySQL is sometimes perceived as a minimalist DBMS, it has a huge potential for creative hacks. The Federated and Blackhole engine, MySQL Proxy, user variables, and some other hooks allow the imaginative developer to achieve impressive results independently from the client's programming language.

MySQL is commonly perceived as a feature poor DBMS. That may be true if you are looking for specific functions or behavior as found in popular commercial database. While lacking 1 to 1 features, MySQL has a flexibility that allows users to achieve the wanted result with a workaround or some settings. But MySQL has much more. Its modular architecture offer to the user a number of creative ways of implementing features, which is sometimes more powerful and affective than the built-in feature of competing databases.

Agenda
In this session, I will show some creative ways of taking advantage of MySQL hidden pearls, regardless of the programming language used in your client.

• Creating custom loops (with MySQL Proxy, with the event scheduler, with Blackhole and cross-joins)
• Creating persistent user variables, either global or user-restricted
• Pushing the limits with Federated tables (multiple triggers, executing remote commands);
• Creating features with MySQL Proxy (customized logs, pivota tables, checking user quotas);
• Using combinations of all the above to achieve unheard of results (e.g. using compressed tables with the efficiency of normal ones, checking passwords strength, downloading and uploading BLOB files, and much more )

Goals
Your imagination is the limit! This session will just give you the raw material and some ideas to get you started.

Overview

The e-Commerce suite of modules (EC) is one of the largest parts of contrib. It is fairly hard to extend, and its main devs are having a hard time evolving it and updating it at the same pace as core.

For most implementers, EC is a turnkey solution, that can work or (too often ?) not, but is not often extended because of its complexity, and possibly the time zone issues with the main developer being located in Oceania whereas most Drupal contributors seem to work in Europe or northern America.

The goal of the session is to identify ways to improve the general experience with EC, by allowing developers wanting to work with/for EC to do so.

Agenda

* Understanding the general operation of the EC suite
* Knowing when to extend EC
* Knowing how to extend EC
* Knowing how to theme EC

Goals

The goal of the session is to enable wannabe EC devs to enter the game, and tempt others who previously renounces to come back to EC.

Resources

Having read the "core" EC source code (product, store, cart) prior to the session would probably go a long way towards making the session helpful for all.

Which version ?

I'm currently planning the session to be based on the (currently alpha) eC 4. Please comment on the proposal if you think we should remain on eC 3 (or for whatever reason).

Overview

Drupal 6 includes a simple lazy-loader for page callback functions. Drupal 7 will feature a completely automated introspective code registry, allowing Drupal to skip the most time consuming part of a page request: The bootstrap. But how can you structure your modules to take full advantage of this new world?

Join Larry Garfield (Crell) and chx (chx) to discuss and develop a set of best practices for module design to take optimal advantage of the registry. Expect some discussion of OOP practices as well, since it's Larry and chx. :-)

Agenda

* What the code registry is and why it is. (Larry and chx)
* What the code registry is not. (Larry and chx)
* OK, so how do we use it? (discussion)
* Draw up recommended guidelines to be included in the handbooks.

Goals

You should come away from this session knowing how to speed up your modules dramatically through a simple cut and paste operation. We also intend to have a publishable set of guidelines for all module developers to help them do the same.

Resources

Past discussion and issues:

http://drupal.org/node/146172 (Drupal 6 page callbacks)
http://www.garfieldtech.com/blog/benchmark-page-split
http://drupal.org/node/221964 (the registry issue)
http://www.garfieldtech.com/drupal-7-registry

Overview

The navigation menu, breadcrumb links, primary links, etc are important for users to be able to navigate your site. Is the way they work in Drupal 6 optimal for usability? Are there better default behaviors we could build for Drupal 7? Could we better accommodate non-standard browsers (e.g. screenreaders)

Agenda

* Fixes up to now (e.g. http://drupal.org/node/270917)
* Default markup
* Your suggestions and input!

Goals

This session will focus on Drupal core, not on contributed modules which can alter or enhance the built-in menus and taxonomy.

By identifying usability problems and possible fixes, this session will hopefully result in some fixes being identified to be addressed in core.

Resources

You should have used a Drupal 6 installation and thought about how you navigate using menus and taxonomy, and how you arrange or assign menu links and taxonomy terms.

If possible, think about "scalable menu parent choosers" and hierarchical select widgets. See: http://drupal.org/node/191360

Usability testing at the University of Minnesota and University of Baltimore suggested that new Drupal users would benefit from more example content in default installations. There are also technical limitations to install profiles which have prevented their widespread adoption in contrib.

This workshop will examine the existing 'default' installation profile, the 'minimum' installation profile (if it's committed by then), and discuss additions to these and other possible profiles for core (single user blog etc.)

The session will also discuss the current limitations of install profiles for developers, and look at alternative mechanisms ('packages', 'install profiles as modules').

Resources:
More defaults in the default install profile: http://groups.drupal.org/node/11691
RFC:Installation profiles as modules: http://groups.drupal.org/node/11548