Re: git-cl upload has stopped working (so has patchy)

[Federico Bruni]

Il giorno dom 31 mag 2015 alle 10:23, David Kastrup <address@hidden> ha 
scritto:
> Personally, I'd consider it better to work with a combined site in 
> this
> respect since it would mean that any tools we develop for our 
> workflows
> (like our own personal git-cl fork) are not LilyPond-only.

IIUC, there's already this tool (not documented):
https://github.com/gpocentek/python-gitlab
> Gitlab is implemented in Ruby, no idea whether that means any of the
> quite-harder-to-make-secure-than-getting-it-up warnings for
> Ruby-on-Rails are applicable here.  It has separate community and
> (non-free) enterprise editions which basically differ in support of
> directory services IIRC.  So that might mean that sharing/integrating
> user management with Savannah might be non-trivial.

Yes, there are cons...

> It does import projects from Github, and Github imports projects from
> Google Code.  So an experimental setup of LilyPond on Gitlab itself
> (which is not totally representative as Gitlab's servers don't run the
> community edition) should be possible pretty easily.  As long as 
> Github
> does not give users the finger who employ its resources for the sake 
> of
> moving a project elsewhere.

Actually, Google Code exports to Github. I tried, just to see what 
happens and it turned out that the standard export works only for 
issues <1000. Here's the FAQ:
https://code.google.com/p/support-tools/wiki/GitHubExporterFAQ#Error_%22Project_cannot_be_migrated_because_it_has_too_many_i

Only an owner on Google Code (I'm a committer only) can try Google 
Takeout:
https://code.google.com/p/support-tools/wiki/IssueExporterTool

I wonder if the JSON dump can contain images...

There's also a script to export to Gitlab:
https://gitlab.com/o9000/google-code-to-gitlab