Toggle RailsBridge Network

Another Successful BugMash Event! Congratulations to the Participants and Prize Winners!

Bugmash Participants help to review 83 tickets in Rails Core Issue Tracker

We had 8 commits to Rails core and over 22 tickets that became ready for Rails Core Team review (this means participants provided patches that haven’t been reviewed by core yet, or issues were mitigated to a point where participants felt Rails Core was equipped with enough information to resolve the issue). We had 55 participants all helping throughout the weekend, including a significant number of first timers. On the whole, we reviewed over 83 tickets!

Congratulations to the participants who won prizes:

  • Jay Pignata has won Rails Rescue Handbook from Mike Gunderloy
  • Joe Van Dyk has won Rails Freelancing Handbook from Mike Gunderloy
  • Matias Flores has won 1 TB Time Capsule courtesy from Blue Box Group
  • Akira Matsuda has won 1 Annual Subscription to Less Accounting from Less Everything
  • John Pignata has won 1 Credit from Peepcode Screencasts
  • sr.iniv.t has won 1 Credit from Peepcode Screencasts
  • John Trupiano has won 1 set of books “Producing Open Source Software: How to Run a Successful Free Software Project” and "The Art of Community: Building the New Age of Participation from Little Stream Software
  • Elad Meidar has won 1 T-Shirt from EngineYard
  • Josh Sharpe has won 1 T-Shirt from EngineYard

A big thanks goes out to all the participants, volunteers, and sponsors that made the event possible and so successful. There were bugmashers and team volunteers in the #railsbrdige chat room the entire weekend, helping each other out.

The final scoreboard can be found here: http://bugmash.com/

For the uninitiated, RailsBridge regularly facilitates BugMash events where all are welcome to contribute to Rails core. Everyone comes together to mash bugs found in the Rails Core Issue Tracker

Participants can help in 4 ways:

  • Confirm that the bug can be reproduced
  • If it can’t be reproduced, try to figure out what information would make it possible to reproduced
  • If it can be reproduced, add the missing pieces: better repro instructions, a failing patch, and/or a patch that applies cleanly to the current Rails source
  • Bring promising tickets to the attention of the Core team

All are welcome to participate. Even if you’re new to Rails, you can lend a helping hand and learn some cool things, too.

Stay tuned for the announcement of our next event!