I'm also on with keeping svn as the VCS of record to make the transition easier. As much as is prefer git,I don't have the energy to drive that conversion.
A different official source for the repo is all that's needed, IMO. Thanks -Ben On Sun, May 31, 2015, 6:45 PM Dagobert Michelsen <[email protected]> wrote: > Hi, > > Am 31.05.2015 um 19:38 schrieb Peter FELECAN: > > Ben Walton <[email protected]> writes: > >> http://helb.github.io/goodbye-sourceforge/ > >> > >> Shall we move our code? > > > > If what's written in the referenced information, why not. > > However, it's not such an easy transition mgar and scm wise. > > Have we the resources to make such a transition? > > Well, the initial reason for using SourceForge as SVN repo was from the > experience with > Blastwave taking down the repo. I don't think it is reasonable to believe > this is a > problem any more. Hosting an SVN repo is not that hard and it would be > good to integrate > that into our existing Trac. As we have raw access to the repo the > transition for > users should be as easy as an "svn switch". Additionally, I don't think we > are in any > hurry, we could also discuss moving to another hoster. Switching the VC > (e.g. to Git) is > a completely different issue I would like to keep out of the discussion > for now. > > > Best regards > > -- Dago > >
