The future of GDocBackup - exporting to GitHub?

[GoogleCodeExporter]

The developer, Fabrizio, seems to have posted a message on the project home 
page (https://code.google.com/p/gdocbackup/), saying that he's officially 
stopping development and support.

So it goes! Many thanks for creating this and your work over the years, 
Fabrizio. Also, extra thanks for making it open source. :)

GDocBackup is the best solution for me out there, and while it seems like it'll 
mostly "just work", issues will undoubtedly crop up. (Such as this one, that I 
just posted: https://code.google.com/p/gdocbackup/issues/detail?id=117)

Not only that, but Google Code is being shut down, as well.

So I wanted to start a discussion here about how best to keep the project 
going! (Even in just a very minimal way: to keep it *working* is the priority, 
not adding loads more features. ;)

First and foremost: Fabrizio, if you have any opinions about this, let us know. 
But I understand you've put the project to one side, and probably don't have 
any time to spend on it. So it's fine if you don't respond to this thread at 
all, but if that's the case, I hope you won't mind if we try to migrate the 
source elsewhere.

I'll do my best to read the (Apache) license, to try and make sure it's not 
violated.

Google Code has an "Export to GitHub" button. I know GitHub's popular, though 
I'm not sure if it's necessarily the best place for this project to move to. 
Either way, it would seem important and urgent to get the source stored in 
*some* other repository before Google Code closes.

I can't spend any time on this for a couple of weeks, but I'll check back in 
then to see what's happening.

Thanks to anyone that can offer any help.

Original issue reported on code.google.com by [email protected] on 29 May 2015 at 6:42