Re: Approaches to forking code

Chris Velevitch wrote:
>
> When you fork code, you need to make 2 decisions: same or different
> repositories and keep or loose the history. But what are the factors
> that would influence these decisions? Would one consideration be: Will
> the forked code base change a little or alot?

If staying in the same repository is a possibility, it is not a fork in
the usual sense and you might as well use a branch that is just never
merged with the trunk. Or, if existing code is going to be developed
into a different program, perhaps you should refactor anything that can
continue to be shared into libraries.

> These are just some of my thinking out loud ideas to help me work out
> what my approach will be, but I guess I'm a little surprised that
> there's nothing formal around on this topic (unless it's under a
> different name) considering that version control and it's principles
> have been around for a long time.

In a real fork, there would probably be new management starting from
scratch deciding what version control package to use. So, you'd be
looking at the conversion tools, or if you stick with subversion it
would be an svnadmin dump, perhaps followed by filtering other projects
out, then loading into a new repository.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1036861
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].