Comments on: 8 steps for fixing other people’s code

By: Dr Nic

Dr Nic — Tue, 04 Mar 2008 22:28:30 +0000

@Michael Klishin [via] - I agree. Amongst the various projects I manage/contribute to the processes for contribution seem to vary. With Subversion there’s really only one way to contribute but with git there various ways. Sometimes the projects will pull commits or whole branches, others will accept patches etc. I’m still not sure which method is best or what the pros/cons are for each option.

I guess the Using Git in Teams article was my initial attempt to throw around some ideas.

I also think there are cool tools coming out to make git easier to use etc. So perhaps those will drive a “best practise” for using git for contributions. Sites like github could also become the defacto standard for using git within a project. Interesting times

By: Michael Klishin

Michael Klishin — Tue, 04 Mar 2008 22:14:06 +0000

Dr. Nic,

I believe modern Ruby community is using Git and Subversion and Git adoption is huge. Maybe update the post?

By: Michael Wood

Michael Wood — Sun, 20 Jan 2008 09:15:20 +0000

In step 6 you say:

If there are any conflicts, go fix them and delete any helper files created by SVN.

I assume you mean the files that Subversion creates to help you fix up the conflict. The way to clean up these files after resolving the conflict is to run:

$ svn resolved path/to/conflicted/file

By: My Hobby is Programming » 8 steps for fixing other people’s code

My Hobby is Programming » 8 steps for fixing other people’s code — Fri, 02 Nov 2007 09:57:53 +0000

[...] read more | digg story [...]

By: links for 2007-09-15 — More Light! More Light!

links for 2007-09-15 — More Light! More Light! — Sat, 15 Sep 2007 06:26:25 +0000

[...] Dr Nic » 8 steps for fixing other people’s code Before or after you’re sharing your own code as open-source, you might find yourself itching to fix someone else’s code. Here is how to do it. (tags: patch opensource programming reference rubyonrails ruby collaboration) [...]

By: Dr Nic

Dr Nic — Fri, 22 Jun 2007 08:01:35 +0000

Added 8d for using LaunchPad Tracker, from Neil Wilson.

By: Warren Seen » Blog Archive » links for 2007-06-02

Warren Seen » Blog Archive » links for 2007-06-02 — Wed, 13 Jun 2007 08:40:36 +0000

[...] Dr Nic » 8 steps for fixing other people’s code Fairly obvious to anyone who’s been using open source software for any length of time, but an excellent writeup. I feel like I should use the word codify here… (tags: programming) [...]

By: Richard White

Richard White — Fri, 08 Jun 2007 01:01:48 +0000

I’m forever honored to be associated with popping your OSS cherry

By: The Programming and Management Blog » Developer Links for 04/05/2007

The Programming and Management Blog » Developer Links for 04/05/2007 — Mon, 04 Jun 2007 19:07:22 +0000

[...] Interesting post about fixing code in other peoples open source projects. 8 steps for fixing other people’s code [...]

By: Jeff

Jeff — Sun, 03 Jun 2007 05:39:40 +0000

Excellent stuff, Dr. Nic. I think it’s hard for some of us to start contributing just because of the fear of the unknown, and this post helped me get a handle on things. Thanks.