> - If I had my druthers[1], I'd stick everything in bzr[2], and
> probably tap Launchpad for primary hosting. That'd let us setup
> team access easily enough. Could setup a local HTTP dumb-server
> mirror beside the website as fallback.
I like Bzr as well, but its future looks rather bleak.
> - Dump it into git and drop it on github. Apparently that's what the
> cool kids do nowadays. Being the In Thing makes it theoretically
> the option that makes it easiest for new contributors to jump in and
> do stuff. Whether that's really a barrier or would be a meaningful
> gain for contributions to a C/Xlib window manager with a rather
> small userbase in its 3rd decade, I look kinda doubtful at but
> express no strong opinion.
I really dislike github and the fact that Git is fashionable
seems irrelevant.
This said, while I'm definitely not in love with Git, it seems it'll be
with us for a long time, and it's establishing itself as the new
standard (the first since CVS), so I'd recommend it for that reason: if
we expect ctwm to live a lot longer but with minimal maintenance, it
makes sense to choose a VCS that will last so we don't have to switch.
Of course, we may prefer not to switch now, but the switch to Git seems
all but unavoidable.
> - ... other options that all seem a lot lower on the likelihood scale.
> Someone here like hg/bitbucket? Resident nutcase big into darcs?
MetaCVS anyone?
Stefan
