{"id":56,"date":"2011-03-23T11:25:44","date_gmt":"2011-03-23T18:25:44","guid":{"rendered":"http:\/\/blog.mozilla.org\/mrbkap\/?p=56"},"modified":"2011-03-27T03:09:38","modified_gmt":"2011-03-27T10:09:38","slug":"how-i-got-started-at-mozilla","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/mrbkap\/2011\/03\/23\/how-i-got-started-at-mozilla\/","title":{"rendered":"How I got started at Mozilla"},"content":{"rendered":"<p>Over in the newsgroups, there&#8217;s a <a href=\"http:\/\/groups.google.com\/group\/mozilla.dev.planning\/msg\/d0bbd32c1139af92\">raging discussion<\/a> taking place about how difficult it is for new contributors to contribute to Mozilla. As part of this sort of discussion, people tend to post &#8220;my first patch&#8221; stories. Rather than reply there, I figured I&#8217;d take this chance to update my blog \ud83d\ude42<\/p>\n<p>When I was in high school, I remember hearing about the launch of Netscape 6 and how it was &#8220;open source.&#8221; Being a budding computer programmer, this was an extremely exciting development. For the first time, I was going to get to see how the &#8220;real programmers&#8221; did things. So, I downloaded the source code and started looking through it. I&#8217;ve always been a &#8220;look first, jump later&#8221; type person, so even once I&#8217;d downloaded the source code and found bugzilla, I lurked. I think I lurked for close to half a year, following bugs that I was interested in by keeping them open and reloading once every few days. Occasionally, if I came across a bug I thought I could fix, I&#8217;d write a patch locally, and wait for the assignee to fix it himself and compare our approaches.<\/p>\n<p>The summer after I&#8217;d graduated from high school, I was looking through the source code and came across the &#8220;htmlparser&#8221; top level directory. Now, this was something I could get my brain around. Somehow, I linked that directory to the HTML: Parser component in bugzilla (probably due to a code comment) and started looking through bugs, commenting in a couple of them when I had something useful to say. After a little bit, I found <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=154120\">bug 154120<\/a>, a small bug in &#8220;view source.&#8221; After having read through the HTML tokenizer code for a while, I&#8217;d seen a few things related to &#8220;view source&#8221;, so I figured out where the bug was and fixed it! I&#8217;d been watching other Mozilla developers working in bugzilla and had observed some of the magic incantations (&#8220;diff -u&#8221; and attaching the result to the bug), but as I was entirely unfamiliar with the process as a whole, I didn&#8217;t realize the importance of requesting &#8220;review&#8221; (as I recall, my hope was that the current assignee of the bug would see the patch and do something useful).<\/p>\n<p>And, nothing happened. I had CC&#8217;d myself to the bug and attached the patch, but had no idea of how to advance my patch further. So, I drifted away and went to college for a year and waited until the next summer, entirely forgetting about the patch I had attached. You can imagine my surprise, then, when out of nowhere, I got several e-mails from bugzilla telling me that some guy named Boris Zbarsky had not only seen my patch, but updated it to the current trunk and found it &#8220;exactly right.&#8221; I still remember the surge of adrenaline kicking in on receiving the e-mail for <a href=\"https:\/\/bugzilla.mozilla.org\/show_bug.cgi?id=154120#c19\">comment 19<\/a> in that bug: &#8220;My code is in Mozilla!&#8221;<\/p>\n<p>What else could I do? I was instantly hooked on that feeling. Having had success with one view-source bug, I found another one and commented in it. Fortunately, Boris was already CC&#8217;d on that one so he could respond and away I went: another (small) bug quickly dispatched, another rush of adrenaline. With Boris to pester on IRC when I had questions and to review my patches (I can only imagine how much I tried his patience, especially in those early days) I was off and running to becoming a developer on Mozilla.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Over in the newsgroups, there&#8217;s a raging discussion taking place about how difficult it is for new contributors to contribute to Mozilla. As part of this sort of discussion, people tend to post &#8220;my first patch&#8221; stories. Rather than reply there, I figured I&#8217;d take this chance to update my blog \ud83d\ude42 When I was [&hellip;]<\/p>\n","protected":false},"author":149,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/posts\/56"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/users\/149"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/comments?post=56"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/posts\/56\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/media?parent=56"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/categories?post=56"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/mrbkap\/wp-json\/wp\/v2\/tags?post=56"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}