[haiku-development] Re: Finally deciding on a new source control system for Haiku
- From: Urias McCullough <umccullough@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 1 May 2011 22:46:31 -0700
On Sun, May 1, 2011 at 7:04 PM, Alex von Gluck <kallisti5@xxxxxxxxxxx> wrote:
>> Would it be crazy to just use GitHub? They are the Git pros, it has a
>> lot of nice tools, it is easy to add and remove collaborators, it is
>> easy to fork and then merge back in changes, it is free for open
>> source projects, it is used by tons of other projects, and more.
>
> +1. Personally I think using github is a great idea. We would save
> a lot of server admin resources going this route. In addition to
> the savings in resources, the code would remain secure as well. One
> really good feature of git is that every developer has a full copy of
> the git repo including logs of every single revision. If the *very*
> worst case scenario occurred and github went under overnight... every
> developer would have a full backup of the git repo (as of their
> last pull) ready to be deployed.
Indeed - the beauty of DVCS is that there's no single failure point -
but rather, and optionally agreed-upon "master" repository.
Moving it to GitHub would be just as satisfactory as maintaining it on
our own servers.
If we ever outgrow it, we can always move it with relative ease (since
most DVCS is generally designed that way) - in the meantime, we could
use the extra server resources to grow other areas of the project.
- Urias
Other related posts:
