Event Status closed
Total Proposals: 83
Thank you for your interest in speaking at the second edition of Garden City Ruby Conference, Bangalore’s own Ruby Conference, to be held on January 10, 2015 @ Bangalore, India. Please follow the below guidelines to boost the chances of your proposal being accepted! If you have questions about the guidelines, you can email us at email@example.com.
You can submit a proposal until November 4th, 2014 at 12:00 AM IST. We'll be accepting talks on a rolling basis, so the earlier you submit, the better the chances are. Our aim is to have the complete program announced by 20th November,2014.
Talks can be for 40 mins or 20 minutes or 90 minutes hands-on Workshops.
For 40 minutes talks, we recommend 30-35 minutes of presentation, followed by 5-10 minutes of questions and discussion.
Workshops are 90 minutes hands-on sessions where participants can learn new things from you along with trying out the same. Please mention any specific setup you expect the participants to have clearly in the proposal.
Please select the appropriate ones from the Tag Options.
We will be receiving lot of proposals and many may be covering the same topic. Knowing what makes a good talk and what helps you best stand out amidst the other proposals competing for the limited spots is important.
Start with a topic that is of interest to attendees. The talk should directly help attendees or inspire/inform them about something they don't already know.
Once you define the topic, define the structure of your presentation. The session should be more than ‘reading out loud’ a blog post/documentation about ‘how to use a gem’. The proposal should clearly state the core value the attendees get from the session.
When you're proposing a talk, we'll ask you to fill out three important fields: the abstract, the details, and the pitch.
The Abstract field is where you write a short paragraph to quickly tell us what you're going to talk about. This gets published in the program along with the title, so it’s the public face of your talk. Clearly mention why should attendees come to your talk and what will they get out of it.
The Details field is for you to go into more depth to us about what you’ll cover. Only reviewers can see it, so it's a good place for things that shouldn't be revealed in the abstract. This is where you can show the review committee what you plan to cover, and how you plan to do it. Also define an outline of your content, the content of your secret sauce, or the twist you’ll include to impress the audience.
The Pitch field is your chance to show the reviewers why you should be giving this talk. Explain why you're passionate about this topic. In this area specifically, please take extra care to refrain from identifying who you are. We understand that it may be most difficult in this section, but we appreciate your efforts at respecting our blind review, as explained below.
Proposals will go through evaluation by the program committee. During the review process, program committee members may have questions for you about your proposal. You'll receive an email notification if there are questions for you. Please reply promptly and consider adjustments when requested. Our committee will have hundreds of proposals to look over, so please make sure that you're not a blocker.
We love first-time speakers and are happy to help you out!
Every proposal submission will be responded to, whether or not the talk is accepted. Please contact us with questions on this only if you have not heard back by November 20th, 2014.
Please use atleast one of the below mentioned tags in the proposal [as part of the tags section] to help the reviewers categorise the proposals.
As many as one-third of the conference attendees would be first-timers. Successful beginner track talks cover topics of interest to new Ruby programmers, but aren't necessarily simplistic. These can include tricks you wish somebody had told you when you were starting with Ruby or parts of Ruby do you think are insufficiently documented, or things most excites you about working with Ruby?
This include highly technical topics on the advanced end of the spectrum. It can include something in the standard library that blows your mind that few use, or interesting techniques no one else knows about or deep dive into Ruby internals.
Even though this is a conference about Ruby, there is value in having non-Ruby talks, but of interest to Rubyists. This could be talks about other programming languages, development techniques etc.