[alsa-devel] Plumbers: Please split audio topics into separate sessions
david.henningsson at canonical.com
Mon Aug 6 22:11:44 CEST 2012
On 08/06/2012 09:29 PM, Takashi Iwai wrote:
> At Mon, 06 Aug 2012 21:09:24 +0200,
> David Henningsson wrote:
>> Looking at:
>> 45 minutes is not enough to handle two topics:
>> Audio uConf: HD-audio cooking && QA/Testing
>> Audio uConf: Expose Routing && DSPs in ASoC
>> Audio uConf: Time Alignment && PA on Android
>> Please split these three sessions into six. It is better to have a
>> little more time than necessary (even if I believe we easily fill 45
>> minutes per topic), than having to skip a topic just because the other
>> topic took more time than expected.
> Well, as already announced, each topic was planned to be about 20
> minutes, so I don't think we need to extend session time.
Judging from our last experience, where we had a two-hour session on
Sunday and then had to reschedule on Wednesday for two more hours, and
yet had to cancel the topic I was about to introduce, because everybody
was tired (and waiting for lunch), I certainly beg to differ!
Besides, I don't remember seeing such a 20 minute announcement. But
maybe I missed it.
> Skipping a topic can be avoided simply by looking at the clock, and
> cut at 20 minutes.
Given the talkative crowd that we are, that might not be so simple ;-)
> Each topic isn't expected to be a big "show" at all. We hope each the
> topic leader shows a couple of slides at most to state the problem and
> the possible solution, and then leads the discussions.
> Of course, it's possible to ask more slots, if you are sure that one
> topic would need really 40 minutes discussions.
It's the discussions that take time.
Also all of the 45 minutes is not effective discussion/presentation
time: Assume that we first wait 5 minutes for all people to appear, then
we have 5 minutes presentation and 15 - 20 minutes discussion for the
first topic, then 5 minutes are spent fiddling with the projector to
show the slides for the second topic...and suddenly there is just a few
minutes left for discussion of the second topic.
Maybe it can be done in 20 minutes in theory, and everything goes as
planned, but it is very overly optimistic.
Also; we fly across half the world to get there, to spend just a few
minutes talking? Better have some margins. Maybe some session will end
early, but will it hurt? No. If we miss a topic, or have to cut it short
without a conclusion, will it hurt? Yes.
> BTW, there is one more slot, planned for my topic for channel mapping
> API. This can be used also for the pending issues, for example.
Given how the scheduler works - it tries to make sure required
participants are not scheduled to two meetings simultaneously -
switching topics and sessions around is going to confuse both people and
the scheduler algorithm.
David Henningsson, Canonical Ltd.
More information about the Alsa-devel