[swirlycheetah]

I tried to participate in 24pullrequests this year but failed on the first day for exactly the reason mentioned in the article; I was forcefully searching for issues to fix in projects where I had no real knowledge of the codebase, the procedures in place or the context of issues raised.

It feels like you'd need to have a wide breadth of knowledge of multiple projects to be able to submit a worthwhile pull requests each day for 24 days.

It'd be interesting to hear from people who did complete the challenge though.

Generally my contributions to other projects have been similar to the OPs, they've come naturally as I've hit stumbling blocks in third party libraries.

[iurisilvio]

I did 24pullrequests last two years. This year, I didn't actively participate (had 8 PR, but not because 24PR). It was a great experience. I tried to find new projects, related to projects I already used.

It is difficult to contribute to Django, Flask, Rails, Linux or any other large project. Look for small and undermaintained projects. They are easier to understand and have more low hanging fruits.

* I started contributing to Postmon (a brazil zip code API) during a 24pullrequests. Now, I'm a core developer of this project.

* I helped with freedomsponsors.org development a lot (the creator is a friend), looked for issues there too and fixed them (counting for 24pullrequests and receiving some money for it).

* Contributed a lot with bottlepy core, bottlepy plugins and Flask extensions

* Fixed some 24pullrequests bugs =)

* Fixed some docs

I wrote about how 24PR help people to increase OSS contribution, using 2013 stats: http://notenoughmemory.com/2013/01/24pullrequests-post-morte...