Fwd: Upcoming Bugmash 9/26-9/27

[Nick Plante]

Thanks to everyone who came out last night. I had a great time, and I think varying the format up a little bit for more interactive sessions like this is a good idea. Thanks to Casey for the inspiration there, and if you want to add your solutions to the group repo let me know and I'll get you access.

Also, I wanted to forward this note on about the upcoming Rails Bugmash in Boston. Let us know if you're planning to attend! It's a great way to learn more about Ruby and Rails, and contribute something to the community at the same time.

Begin forwarded message:

From: Dan Pickett <dan.p...@gmail.com>

Date: September 17, 2009 5:39:28 PM EDT

To: boston-r...@googlegroups.com

Subject: Upcoming Bugmash 9/26-9/27

Reply-To: boston-r...@googlegroups.com

Have you ever wanted to contribute back to Rails? Since our first event in August was such a success, RailsBridge and the Rails Core team will run our next BugMash on September 26th and 27th. If you didn’t participate last month, all are welcomed and encouraged to participate.

For those of you unfamiliar with the Bugmash, it’s very similar to the Rails Hackfests (http://www.workingwithrails.com/hackfest) that were held in 2007 and 2008. Basically, the idea is to reduce the amount of open tickets in the Rails Core Issue Tracker (https://rails.lighthouseapp.com/dashboard), to encourage more people to get involved with the Rails Source, and to have some fun.

We held our first event in August. With over 100 participants, we cleared out 130 tickets.  Even cooler, 35 people had their first-ever patch to Rails accepted. We hope that more people will join in on the fun this time around.

We’ll identify open issues that need help and tag them in Lighthouse, beforehand. During the weekend of the 26th and the 27th, the Rails Core team will be there to incorporate patches and support participants in making the most of their time.

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

RailsBridge is organizing both face-to-face and online support for BugMash participants. The plan is to do everything possible to make it easy to start contributing to Rails, and to increase even further the substantial pool of developers who have helped make Rails what it is.

For more details, including a checklist of what you can do to get ready to work in the Rails source and details on a scoring system and rewards for the most active participants, keep an eye on the RailsBridge Wiki (http://wiki.railsbridge.org/projects/railsbridge/wiki/BugMash).

For now, though, there are few things you can do:
-Reserve at least a chunk of that weekend to roll up your sleeves and work on the BugMash
-Speak up by updating the wiki or posting on the mailing lists ( rubyonra...@googlegroups.com or rails...@googlegroups.com ) if you can contribute prizes, familiarity with the Rails source, or other help to the project.
-Do you know someone or an organization that could supply a prize or sponsor one? Please contact Dan (dpickett -at- enlightsolutions -dot- com) if so. While prizes aren't the focus or the goal, it helps make things fun and competitive.

--
=========================
Dan Pickett
Principal
Enlight Solutions, Inc
http://EnlightSolutions.com

http://www.twitter.com/dpickett

[Brian Buckley]

Nick,  

I'll put our team's solution to the group repo if you give me access.

Thanks for running last night's meeting!  That format worked very well.

Brian

[Nick Plante]

That sounds great. Please email me your github user account and I'll get you added. Same goes for anyone else who wants to publicize a solution (I'll add my own to the nhruby account sometime today, but in the meantime you can view it at http://github.com/zapnap/rubygames)

..nap