| [birt-pmc] FW: [eclipse.org-eclipsecon-program-committee] FW: Track Allocations |
|
All, I just received the EclipseCon Track
allocations. Please see below. My opinion is that we have a little
less than last year but we did pretty well. Does anyone take exception
with the number of allocated tracks? If you do, let me know and I will
take it up tomorrow when we meet.
From: eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx
[mailto:eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx] On Behalf Of Gaff, Doug Hi
folks, The
track allocations have gotten more complicated with our shift to more short
talks. I wanted to explain the allocations prior to tomorrow’s
meeting so you’ll be prepared to discuss. Doug Assumptions -
Actuals from last year make it
impossible to directly convert to this year. o
Last year: 71 long talks, 16
panels, 34 demos, 100 short talks, 87 2hr tutorial o
This year: 80 long talks,
160 short talks, 80 2hr tutorial o
We have a new track (Committer
& Contributor) that also needs talks -
Short talks are a good format for
many things that we may be tempted to put in a long talk. -
Short talks that are grouped can
be used in a variety of creative ways o
4 talks and a 10-minute Q&A or
Panel o
5 speakers on the same theme (time
limits and delineation will be enforced) o
Speedy demos -
50-minute panel talks are of
moderate value and should be chosen carefully (read: do less panels). -
Most demos should be quick
overviews to introduce technology. -
Lengthy demos that are user
focused should be tutorials. -
Bjorn instructed me to reserve
some talks for later allocations and said that quality of recruited content
will open up these extra slots. Color
code (to make mental comparisons easier):
Track
allocation:
|
_______________________________________________ eclipse.org-eclipsecon-program-committee mailing list eclipse.org-eclipsecon-program-committee@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-eclipsecon-program-committee