This is a first and last reminder from us to all of the folks out there that the JavaOne CFP closes on April 15 - just about two weeks from now.
The procrastinator in you might be thinking two weeks is plenty of time. In reality if you haven't started working on your submissions yet, you are probably setting yourself up for some stress that will likely result in a weak submission. This is especially true if like most of us you will need to collaborate with others or get your boss's approval for your submission. Putting things in perspective the CFP has already been open for about a month so other folks already have a hefty head start to maximize their chances of getting accepted.
We have already had some very decent submissions on the Java EE track that has enabled us to get some early acceptances out and gear up the review process as I write this. That being said, we want to make sure everyone in the community has a fair chance to help us build a strong Java EE track agenda by submitting their best ideas. As always, never hesitate to get in touch if you have a question.
Here are some hopefully helpful hints to help you out:
What We Are Looking For
Consider the following as inspiration for submissions to the Java EE track (the only real limits of course are your own imagination on anything in the Java EE ecosystem):
- Existing and upcoming Java EE technology JSRs and implementations
- Cool stuff that extends Java EE in new and interesting ways
- Case studies using Java EE 5, Java EE 6 or Java EE 7 (including migration from other technologies)
- Best practices for using Java EE technologies
- Emerging trends in the ecosystem such as mobile, HTML5, caching, complex event processing, modularity and the like
- Insightful research, development and analysis work in server-side Java
The Cloud Track vs. The Java EE Track
Note that topics like IaaS, PaaS, SaaS, elasticity, multitenancy, NoSQL, Big Data, DevOps and the like should go on the cloud track instead of the Java EE track. Do make an honest effort in applying your judgement on which track to submit on. Either way, it's not a deal breaker if you don't get it exactly right - we will figure it out for you if all else fails. Similarly, please try not to submit talks that really belong in another track such as tools or dynamic languages to the Java EE track. Believe it or not, the Java EE track is actually far more competitive than many of the other tracks. Similarly, if something clearly belongs in the Java EE track, you'll be doing yourself a disfavor by not submitting to the track as the other track leads won't necessarily move your submission correctly.
The Video to Include With Your Submission
Some people are getting caught by surprise that this year we are requiring a video with the submission, so this may bear some explaining. One of the fundamental purposes of the video is to level the playing field for unkown but great speakers. It allows us to assess your submission a lot better by helping neutralize bias towards people that the reviewers are aware of personally. It need not be anything elaborate at all - just a simple explanation of what you are submitting. For experienced speakers, the video requirement is no big deal at all - just submit the video for any talk you have (or ideally video for the talk you are proposing).
Mark Stephens of IDR Solutions recently put out a great blog entry on the JavaOne submission video requirement. The entry is well worth a look.
Don't Count on an Extension
Fortunately or unfortunately some previous JavaOne CFPs have been extended beyond their initial date. Please do yourself a favor and don't assume this will happen again. You may be winding up denying yourself a shot at submitting your great talk altogether :-).
Finally, here is that all important link to the CFP. Hope to see and accept your great topic soon :-)?