Submission tips for speakers
Increase the chance of your talk being accepted
There is generally a very high correlation between how much work one puts into the creation of a proposal and the chance that the proposal is accepted. Even a proposal with an extremely cool theme, entertaining title, and an experienced speaker may be excluded if the description is lacking. We have gathered some tips that should be considered when writing a JavaZone proposal, and a few reasons why proposals may be rejected.
Things to think about when writing your abstract
Create a good titleThe title is the first thing people will see. A poorly worded title may be the only thing many will see of your proposal. A good title is catchy and concise, and should describe what you will talk about.
Write a catchy abstractThe abstract is what will be featured in the JavaZone program for the public to read. If the program committee doesn't believe that the abstract is good enough to convince people to come to your presentation then the proposal won't be accepted.
Provide a detailed outlineThe outline is your chance to pitch the proposal to the program committee. This section will not be published, but if your outline is thin or just a copy of your abstract then you're not selling yourself well.
Be conciseWith an exciting theme, it's easy to find many things one wants to present. Don't get carried away. Your proposal outline should explain how you will cover everything in a clear and structured manner.
Include supporting materialsIf you've held the talk before then please include links to any supporting material that you can show us. This could be video recordings, slide decks, blogs posts, GitHub repositories, photos, etc.
Fill out all mandatory fields properlyNothing says you haven't put much effort into your proposals like a submission form filled with 'TODO' or 'TBD' in the required fields. This is fine for the initial submission, but please make sure the required information is filled out properly by the submission deadline.
Ask someone to review your proposalIf your proposal is full of typos it will be noticed (especially in key fields such as the title). This isn't a point that will necessarily mean the proposal will be rejected, but it doesn't help your case.
Do you plan on doing live coding? Be sure to describe your plan to usLive coding can make a presentation more entertaining, but it also increases the chances of something going wrong. If the program committee doesn't get the feeling that you have a solid plan for the demonstration then it might hurt your chances to be accepted.
Send in multiple proposalsIf you have multiple things you can talk about then submitting 2 or 3 different proposals will increase your chances of finding a place in the schedule.
... but please don't spam usThe program committee reviews hundreds of proposals each year. A few well-written proposals are much more valuable than a bucket full of half-prepared ideas.
Don't shoutYou will definitely be noticed IF YOUR TITLE IS ENTIRELY UPPERCASE (!!!!!!!!), but not necessarily in a positive way.
Why was my talk rejected?
Even though we are rooting for your talk to be accepted, the fact is that some talks must be rejected. Read through these tips to understand why this might happen. Even better, if you are reading this before the Call for Speakers deadline, you can go through your proposal and make sure you do your best to avoid these common pitfalls.