Posted by chx on May 10, 2013 at 7:08pm
Read http://drupal.org/node/756302 how core conversations started in San Francisco. I would like to get back to this: Lightning talks to tell people "my itch to scratch is X" and then after a few of those, have a breakout session where people actually try to figure out solutions to problems. We have devolved these workgroup occasions into just another maybe more technical presentation track maybe with a little bit more of Q&A -- but not enough by far. (If you are a real old hat, remember Antwerp? We were doing the same.)
Comments
Yes, please - the reports
Yes, please - the reports from working groups, etc, have been informative, but scheduling them so much in advance as part of the main program takes away from them being timely and really interactive.
Have either of you actually looked at Portland's?
That's not what we have scheduled at Portland, at all.
http://portland2013.drupal.org/program/sessions/accepted?field_experienc...
One and a half of those might be considered status updates. The rest are all about absolutely critical core process issues that we need to solve.
For "my itch to scratch" and breakout sessions, that's what the coder lounge and BoFs are for, IMO. I don't have the luxury of attending the "coder lounge track," but lots of people do. :) Maybe we need a second coder lounge with a podium and its own BoF/lightning talk calendar?
Also
Anyone who doesn't devote at least half their core convo to Q&A is doing it wrong, both IMO and in the track specifications. :)
Q&A is not what we need
One of the most interesting, most influential core convos at Denver was JohnAlbin's (cos, you know, Twig came out of that). JohnAlbin was talking then we queued up at the mike but the immensely important discussions happened after in the hallway.
In SF, we were discussing testing by sitting in a semicircle and throwing ideas back and forth.