kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #15737
Re: emacs switches to Git
-
From:
Wayne Stambaugh <stambaughw@xxxxxxxxxxx>
-
Date:
Wed, 12 Nov 2014 09:28:11 -0500
-
Cc:
KiCad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAJjB1qLrHCztM=+9E2pWdNeJwh4vBJne4AbnLMhmR-Xk4nreUQ@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
On 11/12/2014 9:01 AM, Mark Roszko wrote:
> git-bzr is buggy
>
> What happened with the svn to git migration that was horrible out of
> curiosity? The only thing I could see is issue tracking? The codebase
> is already migrated because of the git mirror.
The code migration was not a problem. It was the issue tracker and the
knowledge contained in the mailing list. KiCad is much more than it's
code. For a year or so after the move I was still going back to
sourceforge to look things up which was less than convenient. At that
time KiCad had only been on sourceforge for 2-3 years. Kicad has been
hosted on launchpad for the last 6 years, the amount of accumulated
information outside of the source will be significantly more that the
last transition.
>
>
>> What is less clear is the hosting sight. I'm am
>> less than thrilled with using github because AFAIK it is not free
>> software.
>
> Why does it matter? It's extremely easy to switch between them.
> One of the very few "open-source" hosts is https://gitorious.org/ but
> there is no issue tracking and I would advise agaisn't it for that
> alone.
>
> Now if you self-host, you can do Gitlab https://about.gitlab.com/ but
> it requires a bit of a VM or server to run, it's quite the resource
> hog due to its design so for a heavy usage like KiCAD you absolutely
> do not want to run it on a cheap VM without headaches :/
> The alternative is to use Trac and separate git repo manager, it can
> run on a cheap VM no problem.
>
>> Does launch pad support git?
> Nope
>
I consider hosting as important as the chosen vcs. Using a hosting site
based on non-free software may be risky. Anyone remember the
kernel/bitkeeper fiasco? I'm not sure we have the manpower or technical
expertise to host our own git repo.
Follow ups
References