One of the very first documents I read on Git stated something like:
"switching from SVN to Git is like going from black-and-white to
colour TV, once you have it you will not want to go back". If then
this was not so clear, today it makes a lot of sense. Would Git be an
improvement to a project like MASON? Certainly, for instance, having
the contrib packages as sub-modules would greatly ease their usage.
Would Git ease the life for its maintainers? This is not so clear,
I have migrated a few big projects from SVN to Git, I can help with it
Regarding code hosting I would not advise an in-house option. First
because it increases risks of stalling the project, secondly because
there is the social dimension to tap in a code sharing platform. I
know GitHub the best, so that's what I would advise (either with Git
or SVN). Things like patches are way more fun in GitHub than through
the mail list.
Still, if the decision goes for in-housing hosting I would advise
Redmine. It might take some work to install, but once running it is
pretty light on maintenance.
On 12 March 2015 at 19:54, Sean Luke <[log in to unmask]> wrote:
> Well, we have that already in-house. But the work issue is mostly downtime due to power outages, network failures on campus, etc. It's more than you'd imagine.
> On Mar 12, 2015, at 2:11 PM, D. Kriesel <[log in to unmask]> wrote:
>>> - Roll our own. We can do whatever we want. Negatives: I get to be the
>>> administrator. :-(
>> If you do not like Git, I would definitely run my own. Once running, it's
>> not much work and migration is quite easy.