Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipsecon-na-program-committee] Long Talks

I can tell you what I have already scheduled as a long talk:

Tuesday

 

CDO: Satisfy Your Requirements Before You Even Know You Have Them  - We need a long talk for modeling and Eike always does a good job.

_javascript_: Don't Believe the Type!  - based on the long_talk tags

An Introduction to Docker – Invited speaker and Docker is a new topic for the attendees.

 

Wednesday

Modeling SymposiumThey requested the extra time and it is typically popular

JDT embraces lambda expressions – We agreed to give them a long slot instead of two talks.

Go Reactive: Event-Driven, Scalable, Resilient & Responsive Systems – Invited speaker and Jonas will be a popular speaker

 

 

We need to be careful about scheduling too many popular talks at the same time.

 

Ian

 

 

 

From: eclipsecon-na-program-committee-bounces@xxxxxxxxxxx [mailto:eclipsecon-na-program-committee-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
Sent: December-06-13 11:49 AM
To: Eclipsecon NA program committee discussions
Subject: Re: [eclipsecon-na-program-committee] Long Talks

 

I think this is because there were multiple submissions for each topic and we only accepted one. Ian B. mentioned previously that those are candidates for long slots. However, I think the four listed below aren’t good candidates for long talks. I would pick talks that are exceptional interesting. 

 

Another side node, I thought the Modeling Symposium was already set. Thus, reducing the slots to 9. Am I wrong on this one?

 

FWIW, browsing through at the accepted sessions, sorted by avg. rating, here are some picks:

- The Road to Lambda

- API Design in Java 8

- _javascript_: Don't Believe the Type!

- An Introduction to Docker

 

I know it does sound really self-fish …. but I’d like to offer this one too: 

- Unshackling Mylyn from the desktop

 

-Gunnar

 

Am 06.12.2013 um 11:15 schrieb Ian Skerrett <ian.skerrett@xxxxxxxxxxx>:



Fwiw, I am doing the schedule today so I need any recommendations today.  We actually have only 10 slots for long talks since M2M and Vert.x will each get one.

 

There are four talks with the long_talk tag that I was a bit surprised:

 

These didn’t pop out to me as being a long talk so I am interested in understanding why they were tagged? FWIW, two of the talks are from Foundation employees and I usually try not to have Foundation employees taking the prime spots.

 

From: eclipsecon-na-program-committee-bounces@xxxxxxxxxxx [mailto:eclipsecon-na-program-committee-bounces@xxxxxxxxxxx] On Behalf Of Ian Bull
Sent: December-05-13 11:43 PM
To: Eclipsecon NA program committee discussions
Subject: [eclipsecon-na-program-committee] Long Talks

 

The regular speaking slot at EclipseCon is 35 minutes. However, we have 12 'long slots'. These are actually 1 hour slots, although I would expect people to talk for 45 minutes and leave 10 minutes for questions.

 

I've been going through the program and identifying speakers that could make good use of the extra time. Good candidates include interesting subjects, or speakers who submitted several talks on the same subject, but we only accepted one. Since we have 6 long talks each day -- and they happen in parallel -- we should need to ensure that they span different tracks and are not all given by 'rockstar speakers' (I really didn't want to use that term).

 

Go through the program and let me know if you see any talks that should be 'long'.

 

Finally, the crew from Docker has promised me an abstract tomorrow. The docker talk will be given by Nick Stinemates.

 

Cheers,

Ian

 

-- 
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource

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

 

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx



 


Back to the top