24 Pull Requests - Giving little gifts of code for Christmas

First find a project you find interesting, or otherwise worthy. Then, I wouldn't worry about the # of pull requests, just that they have recently accepted pull requests. Once you know they are open to receiving requests, then look at issues to see what low hanging fruit there may be.

Of course, given that it's a one-person project, chances are the code is relatively small and approachable. I think you are much more likely to be able to easily support modify a one-person project than something bigger.

Now, clearly, supporting the code yourself will not always be an option or a good choice; it's just much more likely to be viable with a one-person project.

In case anyone here is interested in contributing to my Django app - https://github.com/freedomsponsors/www.freedomsponsors.org. - That's another free software application intended to make free software even better, one difference is that there are $ bounties involved.

Pull requests are welcome :)

If you do it for Chanuka, you only need 8 pull requests.

When I get involved with projects, I have a lot of potential up front to contribute, and try to do so. Some problems are best handled by those unfamiliar with the project. Examples:

* Documentation fixes - clarifications of parts you find confusing, inconsistencies with current behavior, etc.

* Convention fixes - are most binary checks names IsFoo() but one is named Foo_exists() ? do a quick refactor patch for it. Is one Exception named oddly, or have an unclear message? Patch is quick.

* Examples - does an example highlighting something you're confused about exist? Once you figure it out, whip up an example and contribute. Others are also confused about it - I promise.

* Code commenting - Do the comments contradict the code? Is there something in the code that confuses you? Once you figure it out, fix it and submit.

These are all things that are actually EASIER for newcomers to a project to do - once the quirk has been internalized by a dev, they frequently don't notice it anymore. Particularly with documentation and commenting stuff.

It is harder to do this with giant/super popular projects, but medium and smaller projects can always use this sort of support. For example - I decided to checkout Marionette a couple weeks ago. I was reading the docs and browsing the code to see how something was implemented, and noticed the docs and the code were not in sync. I created and submitted a patch within hours of first learning of the project. This was also a work day, so most of those hours were not spent on anything at all related. The patch was accepted - not a big deal thing, but it was nice to contribute, and it may save someone else half an hour of figuring out what was happening. The dev who merged it actually commented that he didn't realize the docs were out of date - because he knows the code.

Point being, little contributions like this abound. As a project owner, I don't care when contributions are major deals or little tweaks or documentation helpers. I'm just happy when someone contributes, it makes me feel that my project is worth the effort. Which I think may be the point of the idea anyway.