[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Approaches to forking code

From: Matthew Pounsett <matt_at_conundrum.com>
Date: Tue, 20 Jan 2009 00:36:19 -0500

On 20-Jan-2009, at 00:20 , Chris Velevitch wrote:

> I see there is a fair amount of information and discussion on
> branching, tagging, copying and merging but I see nothing on forking.

In my mind the only distinctions between branching and forking are:

1) An entirely separate organization of people will be maintaining the
new code
2) The new code is not expected to retain any similarity to the old
code base

If your use case doesn't match one of those conditions then it's just
a new branch, and I'd recommend you do a cheap copy in the same

I think the above is only likely to occur in a few sets of somewhat
rare circumstances.. such as a group deciding they don't like the
direction an open source project is taking, wanting to fork off their
own project and take it a different way ... or a corporation licensing
another company to repackage or adapt some software.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].

Received on 2009-01-20 06:37:42 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.