[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse.org-eclipsecon-program-committee] EclipseCon 2010: Conference call 30 Dec 09
|
Updates:
Spreadsheets of talk rankings from tag teams are in a shared folder at
[0], named
after the tag. If you are maintaining a spreadsheet, please drop it in
here - you
should have permissions to do so.
I've added a document to this folder called "EclipseCon Talk Slots and
Allocations",
which has the conference layout, the talk slot allocation and times.
The conference
layout and tutorials are set. The distribution of the L/S/E talks is a
suggested one.
Please note there is a set allocation for OSGi DevCon talk/tutorial slots.
SOA/Business and Industry/Modeling tags reviews are complete, in the sense
that the must-haves have been marked in the spreadsheet, inappropriate use
of tags has been eliminated and a selection of 'maybe if we have room' talks
has been selected.
On today's call, I'll be looking for an update on each of the tags
(understood that
some people are still on vacation, or travelling), including a date
for when the
tag team will be complete. If anyone has questions on what to do, give me a
call as soon as you can for an update.
I think we are going to need more than one call before the program date, or
the Big Button, as it was known in the past, so there may be more conference
calls this or next week.
As per Scott's suggestion last week, we need to have a tag-based allocation
that works on three levels - (a) mandatory reserved space, (b) popularity-based
space, (c) discretionary space. I think that this approach is fair, reasonable,
addresses the needs of more diverse projects and gives the PC space for
flexibility.
Let's make sure that we agree that is a reasonable way to proceed.
Here's a proposal for discussion.
There are 21 tags that need allocation slots (OSGi DevCon has them
already, as has the Director's Pick). There are 18 tutorials and 52hrs
of program space to be decided. If each tag is given 1hr of mandatory
reserved space, then that will leave us with 31hrs to be allocated
according to criteria (b, c) above.
Criterion (c) provides us with some flexibility, but it should not be a
large allocation. I suggest 5hrs of discretionary space should be the
target we consider.
Criterion (b) is intended to serve as a rough pro-rata with the popularity
of submissions in a particular tag area. Computing this is a little
fiddly this year, due to the freedom submitters have had with the tags
and the presence of more 'generic' (and unexplained) tags, like Java and
Tools. I'm proposing that we pick a deadline for 'tag cleaning' and divide
the (b) space in rough proportion to the number of submissions to that
tag.
I expect this latter point to be controversial. In all cases it will be
possible to game the system to some extent, but I expect normally
that the gaming is part of the submitter's remit rather than the PC's.
Let's discuss on the call.
I know that everyone is probably a bit hosed busy right now, but I ask
everyone to remember that the Panels are still there to be allocated
and I'll point out that not all were submitted. Let's not forget those in
the rush.
--oh
[0] http://docs.google.com/leaf?id=0B8yVe0iruM6fYjlkYzAzOTgtYjZhOC00Yzg4LWE1NjctZTFjZmIzNmI2ODc0&hl=en_GB