Re: Fwd: Google Code shutting down

[Urs Liska]

Am 13.03.2015 um 11:33 schrieb Han-Wen Nienhuys:
> I guess most of you have seen this by now.
>
> I can click the "export" button so all the issues are migrated to
> github. Thoughts, ideas?
>
> Didn't someone setup a lilypond organization at github?

Yes, that was Janek. But it was considered problematic due to Github's 
unpredictable TOS.
Apart from that: As much as I like working with Github, and especially 
the Pull Request workflows are way more convenient than our Rietveld on 
IMO, the "lightweight issue tracker" is much too lightweight compared to 
our current Google tracker.

Urs

> ---------- Forwarded message ----------
> From: <address@hidden>
> Date: Fri, Mar 13, 2015 at 2:11 AM
> Subject: Google Code shutting down
> To: address@hidden
>
>
> Code
>
> Hello,
>
> Earlier today, Google announced we will be turning down Google Code
> Project Hosting. The service started in 2006 with the goal of
> providing a scalable and reliable way of hosting open source projects.
> Since that time, millions of people have contributed to open source
> projects hosted on the site.
>
> But a lot has changed since 2006. In the past nine years, many other
> options for hosting open source projects have popped up, along with
> vibrant communities of developers. It’s time to recognize that Google
> Code’s mission to provide open source projects a home has been
> accomplished by others, such as GitHub and Bitbucket.
>
> We will be shutting down Google Code over the coming months. Starting
> today, the site will no longer accept new projects, but will remain
> functionally unchanged until August 2015. After that, project data
> will be read-only. Early next year, the site will shut down, but
> project data will be available for download in an archive format.
>
> As the owner of the following projects, you have several options for
> migrating your data.
>
> lilypond
>
> The simplest option would be to use the Google Code Exporter, a new
> tool that will allow you to export your projects directly to GitHub.
> Alternatively, we have documentation on how to migrate to other
> services — GitHub, Bitbucket, and SourceForge — manually.
>
> For more information, please see the Google Open Source blog or
> contact address@hidden
>
> -The Google Code team
>
> Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
> You have received this mandatory email service announcement to update
> you about important changes to Google Code Project Hosting.


--
Urs Liska
www.openlilylib.org