Published on Tuesday, 17 December 2019 19:00
The PEARC20 planning committee has announced significant changes to submission deadlines. The new set of deadlines is listed below, but please check the Call for Participation for the most up-to-date information.
- January 22nd: Tutorial submissions due
- January 22nd: Workshop submissions due
- February 17th: Technical track full paper submissions due
- February 17th: Abstracts due for Lightning Talk submissions
- February 19th: Tutorial and workshop author notifications
- February 24th: Student technology track full paper submissions due
- April 17th: Tech track paper author notifications
- April 17th: Student tech paper track notifications
- April 24th: Poster submissions due (including full manuscripts of a 4-page “poster paper” if authors wish to have a short paper included in the proceedings)
- April 24th: Student posters submissions due (including full manuscripts of a 4-page “poster paper” if authors wish to have a short paper included in the proceedings)
- May 1st: Panel submissions due
- May 1st: BOF submissions due
- May 1st: Viz Showcase submissions due
- May 5th: Poster authors notified
- May 15th: All camera-ready submissions due
- Due in a form that passes the .pdf checking built into Easychair (which means, please do not don’t make your first upload try 2 minutes before the deadline)
- May 22nd: Panel, BOF, and Viz Showcase authors notified
Based on extensive community input, we are going to modify the submission deadlines significantly. The new schedule is set out below. Key points are as follows:
- Almost all deadlines are moved back and staggered. This will avoid situations in which people simply face too many deadlines at once, or worse yet are faced with choosing between working on PEARC submissions and working on one or more of several (around four) proposal submission deadlines that are important to this community
- The deadlines that remain January 22 are tutorials and workshops. The tutorial process has to be finalized before we open registrations for the conference, and if possible we would like to do the same for workshops.
- But the deadlines are deadlines. The posted deadlines are deadlines - the dates “anywhere on earth” by which items in a particular category must be submitted. (And the posted deadline is not a day when the organizers send out a note saying “o.k. folks, we were just kidding about the deadline we posted because we don’t understand what the word means; now it’s time to get serious.”)
- We are aiming for the best technical content we can manage. This means that we will aim for a consistent review score cutoff across the four theme tracks of the conference. (That in and of itself takes some coordination among the track chairs; we understand that and are working on it already). We will adjust the number of papers accepted per track so that the papers we represent the best submitted. Furthermore, we are aiming for a rate of acceptance such that having a paper accepted is an accomplishment that means something. We don’t have a specific acceptance rate target set, but for the sake of argument, what we have in mind is something more like 60% than 90%.
- At the same time, we are going to take several steps to promote inclusiveness, including the following:
- Papers by the first time senior authors and senior student authors will receive special consideration in the review
- We have moved the deadline for student-led papers as late in the process as possible. (“Led” here is important; for papers and posters, the stipulation is that the first author be a student, not just any author is a student.)
- People submitting posters will be encouraged to submit a 4-page “poster paper” to be included in the proceedings (this is an idea copied directly from SIGUCCS). People who submit a full-length paper that is not accepted will be encouraged to present a poster accompanied by a 4 page
- We will have “lightning round” talks for people who want to give a short talk and do not want to do a full paper and full-length proceedings.
Feel free to offer comments and suggestions via email to email@example.com. This change in the schedule is the result of a very well thought out suggestion, backed by significant community input.