Newsletter Sign Up
Stay up to date on all things Rails Rumble! It's easy & opt-in!
The Rails Rumble is a distributed programming competition where teams of up to 4 people, from all over the world, will have 48 hours to build an innovative web application with Ruby on Rails, or another Rack-based Ruby web framework. After the 48 hours are over (and a brief interim to review submissions), a panel of expert judges will each pick his or her 10 favorite entries. All of the expert picks will be combined to find the top 10 Overall Winners, ranked 1 through 10. In addition, voting will be opened to the public for a special, separate, Public Favorite award.
Yes, there are! You can read the official contest rules here.
To read our official Code of Conduct, check here
We ask our expert judges to consider a number of aspects, including: originality, usefulness, appearance, and completeness. However, these categories are not individually rated. Rather, expert judges will consider these aspects when coming up with a list of their 10 favorite entries. Experts will then rank their favorites from 1 through 10 and all expert rankings will be combined to come up with the top 10 Overall Winners.
There are 10 Overall Winners, ranked 1 through 10, picked by our expert judges. Additionally, we’ll be awarding a separate Best Solo award for the best solo entry, according to our expert judges, and a separate Public Favorite award for the most voted-by-the-public entry. Because the Best Solo and Public Favorite awards are separate, you can win one of the overall spots in addition to one of the special awards.
The 2013 Rails Rumble will begin Saturday, October 19th at 00:00:00 UTC (midnight) and continue for the next 48 hours, until Sunday, October 20th at 23:59:59 UTC.
Registration for the 2013 Rails Rumble will be opened on October 7th and will close on October 13th. We’ll open up as many spots as possible, but there will be limited space. Remember — first come first serve.
It’s a virtual sort of thing. That is to say, your team can work from anywhere. Isn’t the Internet great?
Well, a solid grasp of Ruby, Rails, and HTML would be a good start! You’ll also need to have a basic understanding of Git (for source control) and Linux (for deployment of your application). We’ll be providing you with a Git repository and a Linode virtual server for use in the contest.
Aside from expert judges, we’ll also be opening up to the public for a public favorite award. After the build part of the competition is over, you’ll be able to sign up as a judge and pick your favorite entries.
GitHub will be providing free private repositories to each team for the duration of the contest. You must use this repository for development (it’s a great excuse to learn Git if you haven’t already!) and someone from your team must push commits at least twice per day to demonstrate progress.
Each team will have a Linode Virtual Private Server available to them for the duration of the contest and voting period. All applications will be hosted this way. Teams will have to build their own deployment environment. Part of running a successful web application is deploying it, after all! However, we’ll have several aides in place to help with deployment, as well as deployment specialists provided by Linode.
The virtual server will run on Linux from any of the distributions Linode offers.
Part of the beauty of the Rails ecosystem is the widespread availability of helpful gems and plugins. We encourage you to use any third party help that is publicly available. You must credit all applications, gems, and plugins that help your application stay afloat. You can do this in your team profile.
So long as the plugin is publicly available and does not provide the majority of your application’s function. It would be acceptable to develop and release a plugin that provides an interface to an API or builds forms, for instance. It would be unacceptable to hide your controllers and views inside a plugin, “release it”, and install it once the competition begins.
You’re free to plan and design the requirements for your application. You’re also free to work on paper and/or digital UI mockups. You are not allowed to produce any production digital assets or any test or application code prior to the start of the competition. If you have questions, feel free to contact the organizers.
You will be able to install your distribution of Linux prior to the competition but the virtual server will not boot until the competition begins. You will receive your GitHub repository access when the competition begins.
You can, if you want, but it isn’t required that’s for sure. We’ll provide every entry with a domain, something like your-app.r13.railsrumble.com. Also, please note that the *.r13.railsrumble.com subdomained URLs we provide are the official URLs judges will be sent to. If you have a custom domain, you must still support requests coming into the subdomain URL we provide.
The competition does not require it. We hope that some of you will deliver truly innovative web properties during the event; it shouldn’t be a requirement that you share your secret sauce with others unless you want to.
Check out your team profile for all the info you could ever need.
Using commit-hook services is really awesome, but we’re using it to track your code. So feel free to hit up the admin section on your project and add additional commit hook URLs, or deploy keys, but whatever you do, don’t remove our existing ones. Or else we’ll miss your cool awesome work!
The Rails Rumble is the hard work of a few organizers. They wrote the code that runs the contest, coordinate the stuff that needs coordinating, and herd the stray cats.
You can also follow @railsrumble on Twitter or visit #railsrumble on the freenode IRC network, which tends to be a gathering place for developers interested in the Rumble. It’s a great place to find potential teammates and most of the contest organizers also regularly idle in there.
Contact the contest organizers. They’ll hook you up, so you can hook us up.
Contact us and we’ll get back to you as soon as possible.