I think the repo itself is not really an issue because the hooks principles are implemented rather everywhere, and there is always cron as mentioned ;-), and everyone that cloned ghdl has a local copy so it's not lost.
The biggest issue is the wiki, web pages, bug reports, feature requests, associated comments and discussions... those are usually not exportable in a standard way out of the SF/github/etc folks. Hence, not backupable to an independant location that can be used as fallback. How much serious losing all that would be, actually? On Tue, 2015-07-21 at 12:08 -0400, Adam Jensen wrote: > On Tue, 21 Jul 2015 11:28:14 +0100 > Brian Drummond <[email protected]> wrote: > > > > The ideal solution would be one that could be fully > > > replicated/mirrored > > > regularly, like dayly, to an independant location that can be > > > used as > > > fallback. I think it's important to have a reliable fallback > > > location > > I think the distributed approach would be both glorious and > hilarious. > > http://fossil-scm.org/ ***Integrated Bug Tracking, Wiki, and > Technotes*** > > Free hosting available > http://chiselapp.com/ > > and anyone/everyone can easily host a [sync'ed] repo themselves. > http://fossil-scm.org/index.html/doc/trunk/www/server.wiki > > > from http://fossil-scm.org/xfer/doc/trunk/www/selfhost.wiki > --- > Fossil has self-hosted since 2007-07-21. As of this writing (2009-08 > -24) there are three publicly accessible repositories for the Fossil > source code: > > http://www.fossil-scm.org/ > http://www2.fossil-scm.org/ > http://www3.fossil-scm.org/site.cgi > > The canonical repository is (1). Repositories (2) and (3) > automatically stay in synchronization with (1) via a cron job that > invokes "fossil sync" at regular intervals. > > Note that the two secondary repositories are more than just read-only > mirrors. All three servers support full read/write capabilities. > Changes (such as new tickets or wiki or check-ins) can be implemented > on any of the three servers and those changes automatically propagate > to the other two servers. > --- > > _______________________________________________ > Ghdl-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/ghdl-discuss _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
