Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipse.org-eclipsecon-program-committee] Win an Aardvark

We’re not just reading your emails, we’re watching you type them.

 

Update on our Main Stage: thanks to Eric’s diligence in penetrating the Google Bureaucracy (still in Beta), we have recruited the Google developer who built the Android Eclipse Tools. That’s a big win.

 

Our Aardvark talk is a long. (It said tutorial until this morning, but I just fixed that.) We’ll take that prize!

 

+1 for an Industry main stage.

 

From: eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx [mailto:eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx] On Behalf Of Scott Rosenbaum
Sent: Thursday, December 04, 2008 9:55 PM
To: Eclipsecon Program Committee list
Subject: Re: [eclipse.org-eclipsecon-program-committee] Win an Aardvark

 

Eight minutes?  And I thought no one read my emails.  DSDP snatches the carrot before anyone else even moves an inch, doesn't seem fair.  NO TALK FOR YOU!   I am skipping dictator and going straight to despot (imagine maniacal laughter....)

I kill myself sometimes.

I will review DSDP tonight and let you know in the morning. 

Everyone else, do we need to have a second place?  We still have 10 tutorials, 12 longs, and one Main Stage.  You might want to be prepared.

scott



CLONINGER ERIC-DCP874 wrote:

Scott, I think Mobile and Embedded satisfied your criteria at about 11 AM ET this morning.

 

-E

 


From: eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx [mailto:eclipse.org-eclipsecon-program-committee-bounces@xxxxxxxxxxx] On Behalf Of Scott Rosenbaum
Sent: Thursday, December 04, 2008 5:15 PM
To: Eclipsecon Program Committee list
Subject: [eclipse.org-eclipsecon-program-committee] Win an Aardvark

All,

I know you are all hard at work getting your categories in order.  It looks like there are some good negotiations going on to get the submitters to work together and make their talks more concise. 

In case you are wondering how many un-allocated talks are available here is the list:
    - 10 Tutorial Slots
    - 12 Long Slots
    - 1 Main Stage Presentation

On Tuesday's call next week I want to have an Aardvark bake-off.  Each of you will pitch the talks that you can't fit into your allocation that you think should be in the program (aardvarks).  My hope is to distributed the un-allocated talks either on the call or shortly after (email voting).

aardvark pic


In order to make this work, we need to have finished our category reviews.  This means that you should go through your category and:
 - Tentative-Accept the talks you can fit given your current allocation
 - Tag your Main Stage (if you have one)
 - Tentative-Decline talks that we should not consider
 - Tag talks that you think are good, but you can't fit as Aardvark

There is not a lot of un-allocated time to spread between all of the categories so be prepared for some serious horse aardvark trading. 

For this to work we need to be ready.  As an incentive, I will give one long talk to the first category that is ready for the Aardvark sale.  If your category is ready, send an email to the mailing list, I will review and let you know if you have won.  There is a little fine print at the end of the post that explains the rules a bit more.

I realize that I am being a bit of a dictator here.  If you have a problem with that blame Doug Schaefer, I read his dictator post last week. 


Scott




PROGRAM RULES:
over-submitted

1) This only applies to the categories that are significantly over-submitted (see below).  Data Tooling, Reporting, e4, CDT, and Committer And Contrib can not win this one slot.  We still want you to participate in the call on Tuesday, so please make sure you are prepared.

2) No cheating.  You can't just accept a bunch of talks, mark the rest as aardvarks and call it good. 

3) Your category can be over-booked if you have a valid plan to reduce longs to shorts etc.   I am not looking for perfection just a clear idea that your work is done.  If it is confusing explain it in your email (great job to everyone who provided status for the last call).

4) Rules Subject to Change if this poorly thought out idea causes more problems than it solves.

Business And Industry

755%

over-submitted 

OSGi DevCon

659%

over-submitted

Modeling

473%

over-submitted

Tools

471%

over-submitted

Mobile And Embedded

364%

over-submitted

Runtime

349%

over-submitted

Other

327%

over-submitted

Test And Performance

228%

over-submitted

UI / RCP

200%

over-submitted

Emerging Technology

196%

over-submitted

SOA

178%

over-submitted

Java

173%

over-submitted

Web Tools

161%

over-submitted

Data Tooling

117%

not eligible

Reporting

108%

not eligible

e4

101%

not eligible

CDT

100%

not eligible

Committer And Contributor

99%

not eligible



 


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

Back to the top