Skip to main content

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

When do we need to have all of the decline reasons finished by?


---
Andrew Eisenberg, PhD
Senior Software Engineer
Tasktop Engineering

On Tue, Nov 25, 2014 at 2:08 AM, Martin Lippert <mlippert@xxxxxxxxx> wrote:
Hey!

I would like to give people feedback about their rejected talks with a short comment from the PC.
But I will not be able to write all comments on my own, so I will definitely need your help with them.

We will reject about 110 - 115 submissions (from the main five tracks). This includes standard talks and tutorials.
I would like to ask everybody to write rejection comments for 10-11 submissions each and put them into the system.

I think this is a text area called "Decline Reasons”. Is this correct, Anne?

This feedback should be open, honest, polite, and very constructive. I always think about the comment as a way to help them to get a talk accepted next year, asking myself what could be changed/different in order to make it more likely to get a talk accepted next time. Sometimes it is hard to come up with a good comment about the rejection, but maybe Ian (B.) could send around a few good examples from the previous years? As an example? That would be great.

Thanks a lot for your help!!!

Cheers,
-Martin


_______________________________________________
eclipsecon-na-program-committee mailing list
eclipsecon-na-program-committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipsecon-na-program-committee


Back to the top