PC Members,
Thanks for working on this so diligently. I think the program is
shaping up nicely.
From the discussion on
the “Developer Track
Subcommittee” telecon Monday evening. Partitioning the talks should
help
us hone in on finalizing the long talk portion of the program. Note
that not
all of these selections are finalized yet (because in some cases we
need
project feedback, additional discussion, etc.)
Given the difficulty of
picking only 10 additional long talks,
we might want to consider trading in some short talks as well.
I'd really prefer to see a program that does not require trading in
(any? very many?) short talks. The advantage of short talks is that
they give more people the chance to talk about their technology and
their ideas. At a 6-to-1 ratio, the short talks are a good use of
time...
Perhaps we should consider reconfiguring the conference. Right now long
talks are 1 hour. Last year they were 45 minutes. I lengthened them
this year because I felt that 45 minutes was never quite enough for a
good technical talk. But if we shortened them to 45 minutes, we could
have one more session per day for a total of 15 more slots. However, it
means that only 5 x 9 minute short talks would fit into a slot. It
would mean 75 total slots: five parallel tracks of five sessions (plus
lunch, plus keynotes) per day. That's a lot of content - it would make
the program feel tight again. But maybe that's a good thing...
If you are (collectively) interested in this idea, let Tim know and
we'll discuss it on Friday.
I'm sure you know this already, but just a reminder that you don't have
to just accept the "most public voted"
submissions - you are a committer-based meritocracy and you at the top
of that merit tree. Thus you (collectively and using the open source
rules) have
the final say. The public voting is for your guidance; they are like
bug reports (in fact, they are bug reports!) with patch files. You can
choose to accept them or not, based on their merits. If you think a
talk with a lot of votes is not worthy of being in the program - say
so. If you think a talk with few votes is important - say so. In the
end, just like when you write code, your names are associated with the
program content - you will be listed on the website and the printed
program.
Technology
(no specific allocation, but
this seems like too few)
Most of the Technology projects are
candidates for short talks rather than long talks. In my wildest
dreams, I can only imagine long talks from:
If I only get one more, I'd choose PTP - it's a better Technology talk
than ORM.
Everything else can do nicely with a short talk. (I'm sure they'll want
a long talk, but their stuff isn't mature enough to qualify, IMO.)
|
