On Fri, Mar 13, 2015 at 1:37 PM, Trevor Daniels <t.dani...@treda.co.uk> wrote: > > David Kastrup wrote Friday, March 13, 2015 11:51 AM > Subject: Re: Fwd: Google Code shutting down > > >> Graham Percival <gra...@percival-music.ca> writes: > >>> In addition to moving the issues, the "issue handling" scripts would >>> need to be updated. Things like git-cl, patchy, and the whole >>> patch-submission system. That will be a non-trivial effort. >> >> You bet. It would appear like Rietveld will stick around for longer, >> but of course moving away from this Subversion-centric piece of our >> infrastructure would also make sense. But at least we have a different >> time frame for that.
Rietveld is open source https://cloud.google.com/appengine/articles/rietveld that said, it is not very reliable or oriented towards git. Most of the git work at google (eg. Android) today actually uses Gerrit, which a Git-only code review system which is more reliable and performant. Gerrit is open-source, and GNU/FSF could host an instance too. There are hosted versions of these as well, eg. http://gerrithub.io/ > AFAIK the issues database and associated comments are the only > part of Google Code that we, the LilyPond community, use. It is > vital we don't lose this. > > Two questions: > > (a) how do we take a copy of this data base to keep it safe, > including all the follow-up discussions? Making a CSV > copy just seems to download the index. have a look at https://code.google.com/p/support-tools/wiki/IssueExporterTool > (b) Is Google Code open-source or proprietary? It's proprietary. It runs on a host of Google production technologies, such as Bigtable, to be able to scale, and integrates with a bunch of other technologies (Google login, e-mail, etc.) -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
