RE: [eclipse.org-eclipsecon-program-committee] Re:EclipseCon2010Conferen

["Gaff, Doug" <doug.gaff@xxxxxxxxxxxxx>]

Thanks for sending the invitations.

Regrets for this week's call, though. I'm traveling on Thursday.

-----Original Message-----
From: eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx
[mailto:eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx] On
Behalf Of Gaff, Doug
Sent: Monday, October 05, 2009 10:33 AM
To: Eclipsecon Program Committee list
Subject: RE: [eclipse.org-eclipsecon-program-committee]
Re:EclipseCon2010Conference Call Agenda Items 30sep09

Sorry I missed the call. I didn't have it in my calendar.

Anne: would you mind sending invitations for these calls?

-----Original Message-----
From: eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx
[mailto:eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx] On
Behalf Of Oisin Hurley
Sent: Wednesday, September 30, 2009 11:56 AM
To: Eclipsecon Program Committee list
Subject: [eclipse.org-eclipsecon-program-committee] Re:
EclipseCon2010Conference Call Agenda Items 30sep09

Notes from the Call 30sep09

Let me know if I have missed or mis-characterized anything.


Attendees
  Oisin, Donald, David W., David C., Ketan, Doug, Scott

1. Keynotes

* points raised about being cautious with the perception of
entangling sponsorship and keynotes
* a concern about use of an insider for a keynote - better
for panels
* some people go to keynotes to be challenged, and to be
entertained too

Summary - best choice for panels is someone who is
entertaining, without a strong binding to a sponsor :)

2. Panels

* Oisin solicited ideas for panels from the group and pointed
out there are some logistical elements to be considered and
decided upon
* Don pointed out that we need to be definite about our
rules for attendance compensation v.a.v. panels.

Summary:  need to expand more on panel 'rules of
engagement' and start getting the ideas in and recruiting
as well as fee reductions that might be relevant.

3. Tutorials

* Dave said that the most important thing about a tutorial is
that it is hands-on
* Oisin, Ketan mentioned that 2-3 tutorials can work
* Don pointed out that have sessions on the Monday afternoon
could clash with some of the "Monday activities" - the meeting
for the members and the board meeting - causing crowd
dilution. He suggests that we make Monday all-day tutorials
and Thursday all-day sessions. I've added Alternative #3
to the spreadsheet (attached) to show what this would look
like. The Monday panel session makes less sense in this
layout. Your feedback, please. Note that this change means
that attendees have the option of a 4- or 3-day conference.

Summary: please take a look at the option Don has brought
up. My personal preference is to maintain Alternative 2,
keeping it as 4-day affair, for a consistent daily experience.

4. Talks

I got my numbers totally wrong in the agenda mail :)

A number of points here - we're going to get a lot of talks,
so some people will be condensed from long to short. That's
something we have done already in the past. When looking
at talks, we should consider the audience - is it a niche
affair? Then maybe a short talk plus a hint to claim a
slot at the unconference. Short talks have the advantage
that you hear lots of voices, lots of news from different
projects and activities.

My concern here is that we have to make more talk
space, of course. We can cut panels to make this
happen, if necessary.

5. Unconference

Nothing much on this topic. Oisin to follow up with
some approaches to this.

6. Recruiting

I'm interested in forming 2-person groups to recruit talks
related to certain area. Will follow up on the mailing list.

 --oh
_______________________________________________
eclipse.org-eclipsecon-program-committee mailing list
eclipse.org-eclipsecon-program-committee@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-eclipsecon-program-
committee