24 Pull Requests - Giving little gifts of code for Christmas

Post by sophacles » Fri, Nov 30, 2012, 7:08 PM UTC

andrewnez wrote: post #21

sophacles wrote: post #20

Earlier quoted context omitted.

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…

Would it be ok if we used some of these tips as part of the introduction process on the site to help guide people who are new to contributing to open source?

Post by pavel_lishin » Fri, Nov 30, 2012, 8:01 PM UTC

chopsueyar wrote: post #18

samspot wrote: post #11

1 per day for projects I am unfamiliar with seems aggressive. I wonder if I would even be able to add any value with such a shallow understanding of the projects. I think 1/week is probably more reasonable if you are trying to get people who don't contribute to get involved.

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

Post by peteretep » Fri, Nov 30, 2012, 8:36 PM UTC

andrewnez wrote: post #3

The code for the site itself is also open source: https://github.com/andrew/24pullrequests/

Post by noomerikal » Fri, Nov 30, 2012, 9:57 PM UTC

Post by robryan » Sat, Dec 01, 2012, 3:12 AM UTC

smokinjoe wrote: post #9

andrewnez wrote: post #5

Earlier quoted context omitted.

You can suggests projects for people to work on here: http://24pullrequests.com/projects We'll then be sending out regular emails with new suggested projects for people to work on.

This comment has motivated me to join in and give it a shot - I was fairly pessimistic that I wouldn't really know how/where to find projects to work with. Thanks for the idea and best of luck in having it move forward.