On Sun, Oct 17, 2010 at 4:31 PM, steve <[email protected]> wrote: > Besides the other suggestions you have received, I personally feel a more > practical and easier path to contribution is to become a bug-zapper ! ie: > Pick any random application you use everyday (or you can just aim high and > pick the linux kernel itself) and then visit the project's bug tracker. > Almost all open source software has bugs or feature requests that are being > ignored only because the developers either do not have enough tuits [1] or > the bugs aren't critical enough. Pick one or more of those and fix them.
+1 I'd go a step ahead and suggest the 'scratch your itch' approach instead of just lurking on bug trackers, thus not limiting you to any single app. There will surely be something about some application that bothers you -- the odd crash, some behaviour quirk that is just wrong, or some feature you would like to have in it. Download the source for that app, read the code and fix your own problem. Then you contribute your fix upstream. Of course, expect your patch to be rejected at least the first few hundred times. If it is rejected, understand why; that way you learn much more about the app. Somewhere down the line (a couple of years maybe, or more) you will find yourself fixing more bugs of some specific application than others, either because you understand the codebase better or find it interesting/challenging. -- Siddhesh Poyarekar http://siddhesh.in _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
