Mark de Wever <[email protected]>:
> At the FOSDEM we discussed again about whether or not moving to git and
> thus from the location our source repository is hosted. The discussion
> is listed [1] under Git.
>
> Personally I see not too much advantage by Git, git-svn works good
> enough for me. However IMO the uptime of GNA is getting lower over the
> years (it might be selective memory as well).
It probably isn't. I've noticed it as well.
> So moving to another
> place to host our source repository might be a good idea. Am I the only
> one who thinks it would be a good idea to try to find a more reliable
> hosting party? Note moving to another hosting party does not mean
> switching to Git per se.
No, but if we're going to change repo hosting anyway the additional overhead
of changing VCSes is much more tolerable by comparison. Better one clean
break than two traumas.
> How do we feel about moving to Git? As said I see not too much advantage
> by Git, but I'm not opposed to move. If so are there preferences over
> the hosting party? Rhonda also said she can probably host Git for us.
I would be in favor of moving to git. If nothing else it would reduce
incremental update times a lot.
The project would have one unusual advantage in such a move: me! As the
author and maintainer of reposurgeon, and having done several svn-to-git
migrations of large repos to test it, I am probably the most experienced
expert on such migrations anywhere. The fact that I know Wesnoth's history
pretty well is a nice bonus.
On the other hand, one of the things that experience tells me is that
a Wesnoth migration would be a huge, messy project. The sheer size
of the repo would produce a scale problem in itself - a full download of
all branches runs my development machine out of disk space!
This doesn't mean it can't be done. It does mean it can't be done
*quickly*. But we probably want to wait until I ship reposurgeon 2.0
anyway; I'm still chasing some bugs in the svn support.
> If we decide to move, do we only want to move the source repository or
> also the bug-tracker and mailing lists? I haven't investigated whether
> or not it's possible to export our bug-tracker's contents.
I have written a tool that can scrape the GNA bugtracker. The problem isn't
export but import - loading it into anywhere else. It is probably not
yet feasible to move the tracker.
However, I think we should probably begin preparing for a move. Gna
is understaffed and undermaintained, and the Gna codebase is creaking
and old. I would feel much more secure if the repo were migrated to
somewhere like github or gitorious.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
