Rails 3 BugMash Outcomes

Last weekend, we had another successful event. People seemed to respond really well to the loose structure around doing something for Rails 3, whether it’s a blog post, testing a plugin, or filing bugs.

There were 47 submissions reported from 26 people. We’ve drawn prizewinners, and we are reaching out to them directly to match them up with our sponsors. Once we contact them, we’ll publish a list.

We were thankful to have significant core team involvement. Core team members were in the IRC channel for good portions of the weekend. It seemed like there was a lot of healthy. positive conversation about style, convention, and architecture.

Here are some highlights:

• Josh Nichols worked successfully to get Moonshine (a deployment/instance generation tool) working with Rails 3 – http://github.com/railsmachine/moonshine/tree/rails-3
• We started a wiki of plugins and gems that are Rails 3 ‘ready’ here
• Jon Trupiano helped to make factory_girl Rails 3 ‘ready’
• Sarah Allen organized a team of locals together to explore Rails 3 – the team’s findings can be found @ http://blazingcloud.net/2010/01/17/notes-from-rails-3-bugmash/
• Jeff Kreeftmeijer got navvy (an increasingly popular background job processor) running on Rails 3 – http://wiki.github.com/jeffkreeftmeijer/navvy/installation-on-rails-edge
• Ryan Bigg attacked the Rails Guides with success – https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/3702-all-guide-content-should-be-accepted-as-html_safe

There were a number of cases where people were talking about twitter and IRC that went undocumented. If you helped out, we’d love to hear your feedback and your thoughts on how we can make these more general events run better.

Thanks to our sponsors and participants for helping to truly make Rails 3 better! Let’s keep mashin’.