Call for Papers
We are now accepting proposals for PGConf.EU 2020!
All selected speakers will get free entry to the conference (excluding training sessions) but do need to register. We do not in general cover travel and accommodations for speakers, but may be able to do so in limited cases. If you require assistance with funding to be able to attend, please make a note of this in the submission notes field.
Each session is 45 minutes after which there will be time for questions. We may also have a limited number of longer, 90-minute, slots available. Please indicate clearly in your submission if you wish to present a 90-minute talk. All presentations have to be in English.
The submission deadline is July 31st, 2020 at 24:00 in Berlin, Germany. Selected speakers will be notified before August 21st, 2020.
Talks may be on any topic related to PostgreSQL in some way. Suggested topic areas include:
- Developing applications with or for PostgreSQL
- Administering large scale PostgreSQL installations
- Case studies and/or success stories of PostgreSQL deployments (or interesting failures)
- Tools and utilities
- PostgreSQL internals hacking
- Community and local user groups
- Tuning and performance improvements
- Migration from other database systems
- Replication, clustering and high availability
- Recovery and backup strategies
- Benchmarking and hardware
- PostgreSQL related products
- DevOps and continuous deployment/configuration/integration around PostgreSQL
…of course, we're happy to receive proposals for talks on other PostgreSQL related topics as well.
As usual, there will be a session of five minute long lightning talks. A separate call for proposals will be made for them at the conference itself so bring your slides!
Harald Armin Massa
Stefanie Janine Stölting
We look forward to hearing your story!
We are often asked about the selection criteria and process for selecting the presentations among all the submitted proposals that will make up the schedule.
All submissions are looked at and considered by the program committee by reading abstracts, titles, and submission notes. The program committee members each vote on every submission with a score of 1 through 9. It is customary to abstain from voting on submissions by coworkers. When a presenter has multiple submissions, the committee considers which subject will be the best fit for the conference as we try very hard to not have repeat speakers during the event. Submissions are also de-duplicated to minimise repetition, such that the schedule is balanced overall.
Program committee members are — like every other position in the PGConf.EU organisation — an unpaid volunteer position. There are more than 250 talk submissions every year so spending just two minutes per abstract takes in excess of 8 hours, not counting sorting, comparing and grouping by same topic, etc.
The talks are then sorted by their average score and the final selection is made by the committee in conference calls amongst the top rated.
It has shown over the years that a clear and concise abstract is a good indicator of a clear, understandable thought process and well received presentation. The program committee thus puts a very large emphasis on the abstract. To improve your chances of being selected for PGConf.EU:
- make sure the abstract is clear and to the point;
- show the knowledge that will be gained by the audience;
- be concise, do not post a full script.
Do not keep secrets or surprises from the committee. If your abstract teases the audience about some research or a new project you are planning to reveal during the talk, make sure you tell the committee what that is in the submissions notes. Your secrets are safe with us, but we need to know what the content of our conference is.
How clear is the connection to PostgreSQL? Broader topics are of course welcome, if the connection to PostgreSQL is made clear. Known speakers are generally more trusted to connect to PostgreSQL on general topics, so if in doubt make sure to include in the abstract how it relates to PostgreSQL.
It is also important to not try to cover too much ground in a session; there is only so much the audience can absorb in 45 minutes. Trying to cover every GUC in a single talk is, while most likely feasible, unlikely to translate well into a live presentation.
Presentations about potential future features in PostgreSQL should also make it clear in the submission notes where the patch is currently. Is it in a CommitFest or is it still under heavy development?
Submissions about a commercial service offering, or product demonstrations, are not good fits for the main tracks at PGConf.EU. They are however very good candidates for the Sponsor Track where we do allow these types of presentations. If you are interested in submitting to this track, make sure to sign up as a sponsor at the required level first as only confirmed sponsors can submit.
Make sure to be very clear in your speaker profile, and supply your full name within the submission process. Although your followers on social media may know you as xyz, that might not be true for all the members of the program committee and/or the conference participants. If the speaker profile explains why your are the best speaker for the proposed topic, that is of tremendous value. As the profile is published for all scheduled talks, that may also help attendees select your talk when planning their day at the event.
Travel Sponsorship and Location Requirements
If you require or request anything, please be upfront and open about it in the submission notes, for example if a whiteboard is needed or if travel reimbursement is required for you to attend. We aim to make PGConf.EU as affordable as we can for everyone, but that means that we are unable to fund all speakers for travel and accommodation. The norm is that all regular speakers organise and fund their travel by themselves. If you do require help with travel in order to attend, please let us know and we will do what we can to help you should your talk be accepted.