Thank you for your interest in speaking at RubyConfIndia 2016! The conference will be from March 18-20, 2016 in Kochi City, Kerala state in India. We're looking forward to seeing all your proposals!
Please read these guidelines all the way through for the best chance of having your proposal selected. If you have questions or concerns about anything you see here, please don’t hesitate to email us at email@example.com
We will be doing "rolling acceptance," so submit early, and your talk may be accepted early!
If you have not heard about the status of your submission after that time, please contact us. Thanks!
Regular talks are 25-minute blocks, including any Q&A you want to do.
If your session is selected for inclusion in our program, you get:
Free admission to the conference.
Twin occupancy room (you will share a room with another speaker) at Le Meridien, Kochi.
The respect and adulation of your peers!
The opportunity to be paired with a speaker mentor before the conference to help you with talk prep. This will be automatic if you're a new speaker, optional for experienced speakers, and highly recommended for everyone.
We reserve ticket space for folks whose talks are not accepted, so you can wait on buying a ticket until you hear about the status of your talk.
We have a program committee made up of hardworking volunteers representing a variety of experience levels with Ruby/Rails. Our first round of review is blind, meaning reviewers will not see your name or biographical information. They will see the title, description, pitch, and abstract. Please keep any potentially identifying information out of these fields.
During this first round, reviewers may have questions for you about your proposal. The CFP application allows two-way correspondence in comments without revealing your identity (though you'll know who's asking the question). You'll get an email (and see a notification on the site) if there are questions for you. Please reply promptly and consider adjustments, if requested.
Once every talk has at least three ratings, we move into the second round, where we evaluate highly-rated talks alongside their biographical information (speaking experience, relevant credentials, etc.) to come up with a balanced program. The program committee is heavily committed to selecting a diverse and well-qualified group of speakers.
In speakers: a diverse and creative line-up of speakers with a range of experience levels (in Ruby, in programming, and in public speaking).
In talks: a range of topics, both occupational (i.e., about Ruby, Rails, code-heavy, etc.) and organizational (i.e., about team dynamics, communication, etc.), and all applicable hybrids. We want talks aimed at developers coming from a wide range of experience levels, from beginner-friendly how-tos to cautionary tales to deep dives for experienced devs. We want talks about all the different parts of the Ruby/Rails ecosystem, including related technologies (data stores, front-end frameworks) and related teams (QA, product management, clients).
Thank you for making it this far. :) We will be receiving hundreds of proposals, many covering the same topics. Reading the following will help you craft a proposal that stands out.
Start with a topic of interest to attendees. Our attendees are generally Ruby/Rails developers at many different levels of experience, from totally new to very experienced. Your talk should either directly help them, or inspire/inform them about something they don't already know. The core value to our attendees of what you're presenting should be clearly stated in your proposal. What will they be able to do after they see your talk that they can't do now?
Our proposal form has two fields that attendees will see on the program (title and abstract), and two fields that only our reviewers will see (details and pitch). Here are a few more details on each.
These are what attendees will see in the program. Title and abstract should be compelling and to-the-point. Tell a story. Why should attendees come to your talk and what will they get out of it?
Reviewers will see your title and abstract, and also your details and pitch. Details is a good place to go into more depth about what you'll cover. It's a good place to put an outline, reveal the secret sauce, and explain any twists you'll include in your talk that may not be evident in the title or abstract.
Pitch is a good place to tell reviewers why RubyConfIndia needs this talk, and why you're the right person to give this talk at RubyConfIndia. How will your talk help the program, or fill a specific need? Why are you excited about this topic? Please take extra care here to refrain from identifying who you are. As mentioned above, our first round of review is blind, and we appreciate your efforts to respect that.