BugMash

Version 71 (Eric Davis, 09/26/2009 06:32 am)

1 20 Eric Davis
{{>toc}}
2 20 Eric Davis
3 60 Mike Gunderloy
h1. NEXT BUGMASH SEPTEMBER 26-27, 2009
4 60 Mike Gunderloy
5 1
h1. BugMash
6 1
7 1
Have you ever wondered how you could get started contributing to the core Rails code? Have you been watching the growth of RailsBridge and wondering where you could fit in? Well, wonder no longer: we have an answer to both of those questions. Announcing:
8 1
9 1
h2. The First Rails and RailsBridge BugMash
10 1
11 2 Eric Davis
The idea is simple: RailsBridge has a lot of energy. "The Rails Lighthouse":https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets?q=all has a lot of open tickets. With the help of some Rails Core team members, we're going to see what we can do to cut down the number of open tickets, encourage more people to get involved with the Rails source, and have some fun.
12 1
13 1
# Confirm that the bug can be reproduced
14 7 Dana Jones
# If it can't be reproduced, try to figure out what information would make it possible to be reproduced
15 1
# 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
16 1
# Bring promising tickets to the attention of the Core team
17 1
18 34 Eric Davis
Some of the Bridgers will be organizing a face-to-face way for BugMash participants to come together ([[BugMash#Teams|Teams]]), but there's no need to be there to be a part of it. We'll also have a room open on IRC, and people who are familiar with the Rails internals will be available to help point you in the right direction. We're going to do everything we can to make it easy to start contributing to Rails.
19 1
20 2 Eric Davis
We'll be adding more details to this bare outline over the coming week, 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. For now, though, there are two things for you to do:
21 2 Eric Davis
22 2 Eric Davis
# Reserve at least a chunk of that weekend to roll up your sleeves and work on the BugMash
23 2 Eric Davis
# Speak up if you can contribute prizes, familiarity with the Rails source, or other help to the project.
24 3 Mike Gunderloy
25 4 Mike Gunderloy
h2. Official BugMash hours
26 1
27 60 Mike Gunderloy
Rails contributors are located all over the world, so we're going to define an extended weekend for the BugMash. So we're going to run from Saturday noon in New Zealand (00:00:00 September 26 GMT) to Sunday midnight on the US West coast (07:00:00 September 28 GMT). That should give everyone who wants to be involved plenty of time to participate.
28 6 Mike Gunderloy
29 4 Mike Gunderloy
h2. Resources
30 4 Mike Gunderloy
31 4 Mike Gunderloy
* [[Pre-flight Checklist]]
32 37 Mike Gunderloy
* [[BugMashFlowchart]]
33 68 Mike Gunderloy
* [[BugMashCheatSheet]]
34 4 Mike Gunderloy
* "Contributing to Rails":http://guides.rubyonrails.org/contributing_to_rails.html
35 38 Mike Gunderloy
* "Tickets tagged with 'bugmash'":https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/bins/41908
36 70 Chad Woolley
* There are official Rails Continuous Integration servers which test against multiple interpreters and databases.  See the Continuous Integration section in the [[BugMashFlowchart]]
37 67 Chad Woolley
* The Rails "Continuous Integration Server Setup Notes":http://github.com/rails/rails/blob/master/ci/ci_setup_notes.txt can be helpful in getting the various databases configured
38 22 Mike Gunderloy
* http://railscasts.com/episodes/113-contributing-to-rails-with-git
39 44 Mike Gunderloy
* [[BugMashStats]]
40 26 Mike Gunderloy
41 26 Mike Gunderloy
h2. Teams
42 26 Mike Gunderloy
43 26 Mike Gunderloy
We're not doing team-based scoring, but we do have people getting together in various cities.
44 26 Mike Gunderloy
45 61 Dan Pickett
* "Seattle, thanks to Blue Box Group":http://www.blueboxgrp.com/news/2009/09/blue_box_group_to_sponsor_rails_bugmash
46 61 Dan Pickett
* São Paulo, Brazil
47 26 Mike Gunderloy
48 66 Dan Pickett
If you're interested in one of these, or want to organize your own in-person event, drop by the #railsbridge IRC channel to chat.
49 66 Dan Pickett
50 64 Dan Pickett
h2. Prizes 
51 64 Dan Pickett
52 65 Dan Pickett
* 1 TB Time Capsule courtesy of "Blue Box Group":http://www.blueboxgrp.com/news/2009/09/blue_box_group_to_sponsor_rails_bugmash
53 64 Dan Pickett
* 1 Annual Subscription to "Less Accounting":http://lessaccounting.com/ and "Less Time Spent":http://lesstimespent.com/
54 64 Dan Pickett
* 1 Annual Subscription to "Less Accounting":http://lessaccounting.com/ and "Less Time Spent":http://lesstimespent.com/
55 64 Dan Pickett
* 1 Credit for "Peepcode Screencasts":http://www.peepcode.com
56 64 Dan Pickett
* 1 Credit for "Peepcode Screencasts":http://www.peepcode.com
57 71 Eric Davis
* 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":http://www.littlestreamsoftware.com
58 64 Dan Pickett
* 1 copy of Mike Gunderloy's "Rails Rescue Handbook":http://www.railsrescuebook.com/
59 26 Mike Gunderloy
* 1 copy of Mike Gunderloy's "Rails Freelance Handbook":http://www.railsfreelancebook.com/
60 4 Mike Gunderloy
61 4 Mike Gunderloy
h2. IRC support
62 6 Mike Gunderloy
63 11 Mike Gunderloy
We'll have experienced Rails developers and core team members available on IRC for as many hours during the BugMash as humanly possible. If you're having trouble getting started, want to brainstorm about a particular ticket, or can help other people out, please come by and join us. We'll be hanging out on the #railsbridge channel on Freenode IRC. Our [[IRCGuide]] can help you get connected.
64 11 Mike Gunderloy
65 43 Mike Gunderloy
We also have a bot who's helping us keep track of who's working on what. Details at [[BugMashBotUsage]].
66 17 Mike Gunderloy
67 6 Mike Gunderloy
h2. LightHouse Mechanics
68 17 Mike Gunderloy
69 35 Eric Davis
Some of the Rails core team members will go through the open issues in Lighthouse and add the "bugmash":https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/bins/41908 tag to tickets that they're especially interested in seeing tackled. This will allow you to use a Lighthouse query to find interesting tickets. You're not required to stick to those tickets, but they're a good starting point.
70 38 Mike Gunderloy
71 38 Mike Gunderloy
Note that some of the tagged tickets are marked as "stale" or "incomplete," and Lighthouse will show them with a strikethrough in list view. _These are still fair game for the BugMash!_ We're hoping to take a second look at some of the issues that have been in a holding pattern for a long time.
72 4 Mike Gunderloy
73 4 Mike Gunderloy
h2. Scoring
74 4 Mike Gunderloy
75 18 Mike Gunderloy
25 pts for every +/- 1 (awarded to the commenter not the ticket creator)
76 18 Mike Gunderloy
50 pts for every verified/not reproducible (awarded to the commenter)
77 18 Mike Gunderloy
50 pts for a new ticket
78 18 Mike Gunderloy
100 pts for supplying a test case/patch
79 18 Mike Gunderloy
1000 pts for every changeset
80 18 Mike Gunderloy
81 18 Mike Gunderloy
Quick example:
82 18 Mike Gunderloy
83 18 Mike Gunderloy
hardbap opens ticket "HasOneThroughAssociation should not be a child of HasManyThroughAssociation", +50
84 18 Mike Gunderloy
includes a world class patch,  +100 for hardbap
85 18 Mike Gunderloy
mikeg verifies the patch, +50 for mikeg
86 18 Mike Gunderloy
hobbs +1, +25 for hobbs
87 32 Mike Breen
hardbap's patch is committed to core with gusto by lifo, +1000 for hardbap
88 18 Mike Gunderloy
89 18 Mike Gunderloy
hardbap's total for the ticket = 1150
90 33 Eric Davis
mikeg's total for the ticket = 50
91 33 Eric Davis
hobbs's total for the ticket = 25
92 18 Mike Gunderloy
93 18 Mike Gunderloy
For every 100 points, you'll get 1 ticket in the lottery to distribute the prizes.
94 18 Mike Gunderloy
95 57 Dan Pickett
h2. Past Events
96 1
97 58 Dan Pickett
* [[2009-08]]
98 52 Mike Gunderloy
99 45 Elad Meidar
h2. Participants Testimonials
100 45 Elad Meidar
101 45 Elad Meidar
* "Rails BugMash on RailsBridge":http://blog.eizesus.com/2009/8/rails-bugmash-how-i-fell-in-love-again - ".. witnessed the mission and statement of #railsbridge coming true in the very first time they were put to the test. ..." - Elad.
102 46 Philip Ingram
* "Lessons I learned about Rails from the BugMash":http://ingraminternet.com/posts/3-lessons-learned-about-rails-from-bugmash-09 - I describe the lessons that I learned during the BugMash about Rails and the rails community - Philip.
103 47 Peer Allan
* "Rails Bugmash August 2009: Before, During & After":http://www.allanweb.ca/2009/08/11/rails-bugmash-august-2009-before-during-after/ - Peer
104 52 Mike Gunderloy
* "Rails Bugmash: sweet":http://elisehuard.wordpress.com/2009/08/16/rails-bugmash-the-roundup/ - "Not only was it very instructive, it was also lots of fun, like resolving chinese puzzles in group, and against a clock. " - Elise
105 63 Irina Dumitrascu
* "fixed bugs for fun: Rails BugMash":http://www.dira.ro/blog/2009/08/will-fix-bugs-for-fun-rails-bugmash/ - "Big Kudos to RailsBridge for organizing the event and easing the ‘contributing to Rails learning curve’. It allowed me to use my Ruby & Rails skills to the max, even if it was the first time I contributed." - dira