Fwd: Google Code shutting down

newer
Re: [tei-council] Google Code...

older
Dates now fixed for F2F?

Hugh Cayless

12 Mar 2015 12 Mar '15

6:29 p.m.

This affects the TEI Oxygen framework. GitHub anyone? Sent from my phone. Begin forwarded message:

...

From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

Show replies by date

James Cummings

13 Mar 13 Mar

3:10 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand. -J On 13/03/15 01:29, Hugh Cayless wrote:

...

This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

James Cummings

4:12 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

On a related note there is another project on google code https://code.google.com/p/tei-enrich The ENRICH schema was a customisation of manuscript description for the ENRICH project attempting to standardise use of msDesc across a large number of libraries in the EU, forming a basis for manuscriptorium.com and input to europeana. I believe we make the tei-enrich schema available in the oxygen-tei framework. My plan was to migrate this to the TEIC github organisation. Any objections to that? Since it was an international project it sort of makes more sense than sticking it in the ox-it organisation or any individual. -James On 13/03/15 10:10, James Cummings wrote:

...

Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford

Peter Stadler

5:42 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

No objections from my side. I think we decided *not* to be responsible for everything that’s under the TEI-C umbrella … Cheers Peter

...

Am 13.03.2015 um 12:12 schrieb James Cummings :

On a related note there is another project on google code https://code.google.com/p/tei-enrich

The ENRICH schema was a customisation of manuscript description for the ENRICH project attempting to standardise use of msDesc across a large number of libraries in the EU, forming a basis for manuscriptorium.com and input to europeana.

I believe we make the tei-enrich schema available in the oxygen-tei framework.

My plan was to migrate this to the TEIC github organisation. Any objections to that? Since it was an international project it sort of makes more sense than sticking it in the ox-it organisation or any individual.

-James

On 13/03/15 10:10, James Cummings wrote:

...
Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

James Cummings

6:23 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

Actually it seems we already are in that we have it as an exemplar in TEI sf svn and build it with Jenkins and release it. So maybe that Google code repo should just freeze and die. James -- Dr James Cummings, Academic IT, University of Oxford -----Original Message----- From: Peter Stadler [stadler@edirom.de] Received: Friday, 13 Mar 2015, 12:42 To: tei-council@lists.tei-c.org [tei-council@lists.tei-c.org] Subject: Re: [tei-council] Fwd: Google Code shutting down No objections from my side. I think we decided *not* to be responsible for everything that’s under the TEI-C umbrella … Cheers Peter

...

Am 13.03.2015 um 12:12 schrieb James Cummings :

On a related note there is another project on google code https://code.google.com/p/tei-enrich

The ENRICH schema was a customisation of manuscript description for the ENRICH project attempting to standardise use of msDesc across a large number of libraries in the EU, forming a basis for manuscriptorium.com and input to europeana.

I believe we make the tei-enrich schema available in the oxygen-tei framework.

My plan was to migrate this to the TEIC github organisation. Any objections to that? Since it was an international project it sort of makes more sense than sticking it in the ox-it organisation or any individual.

-James

On 13/03/15 10:10, James Cummings wrote:

...
Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived

Fabio Ciotti

6:28 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

...

Actually it seems we already are in that we have it as an exemplar in TEI sf svn and build it with Jenkins and release it.

So maybe that Google code repo should just freeze and die.

Rest in piece... f

Martin Holmes

5:39 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

I'll have to fix the build job for the dev version of the plugin on Jenkins too. Sebastian, can you let me know when it's done and working? My GitHub id is martindholmes. We'll have to add all the Oxygen folks too. Cheers, Martin On 15-03-13 03:10 AM, James Cummings wrote:

...

Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

Kevin Hawkins

20 Mar 20 Mar

9:10 p.m.

New subject: [tei-council] Fwd: Google Code shutting down

I've updated http://wiki.tei-c.org/index.php/OXygen#Support_for_TEI to point to the sourcecode on GitHub instead of Google Code. Will ZIP files continue to be created at https://sourceforge.net/projects/tei/files/tei-oxygen/ ? If so, we'll need to edit this section of the wiki. Likewise if the directions for subscribing to the TEI framework have changed. Kevin On 3/13/15 5:10 AM, James Cummings wrote:

...

Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

Martin Holmes

21 Mar 21 Mar

9:24 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

Hi Kevin, Instructions for subscribing should not change as a result of the move to GitHub, but we have agreed that we'll re-title the project "oxygen-tei" instead of "tei-oxygen" because the former is the name of the project on its repo, and the latter is already in use as the name of a deb package. Whether we do this before or after the next P5 release hasn't been decided. What do we think? Cheers, Martin On 15-03-20 09:10 PM, Kevin Hawkins wrote:

...

I've updated http://wiki.tei-c.org/index.php/OXygen#Support_for_TEI to point to the sourcecode on GitHub instead of Google Code. Will ZIP files continue to be created at https://sourceforge.net/projects/tei/files/tei-oxygen/ ? If so, we'll need to edit this section of the wiki. Likewise if the directions for subscribing to the TEI framework have changed.

Kevin

On 3/13/15 5:10 AM, James Cummings wrote:

...
Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

Kevin Hawkins

9:29 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

I agree that those two names are confusing, but I think "oxygen-tei" and "tei-oxygen" are still easily confused. It would be nice if we could come up with something even more distinctive. In any case, I don't have an opinion on renaming before or after the next P5 release. K. On 3/21/15 11:24 AM, Martin Holmes wrote:

...

Hi Kevin,

Instructions for subscribing should not change as a result of the move to GitHub, but we have agreed that we'll re-title the project "oxygen-tei" instead of "tei-oxygen" because the former is the name of the project on its repo, and the latter is already in use as the name of a deb package.

Whether we do this before or after the next P5 release hasn't been decided. What do we think?

Cheers, Martin

On 15-03-20 09:10 PM, Kevin Hawkins wrote:

...
I've updated http://wiki.tei-c.org/index.php/OXygen#Support_for_TEI to point to the sourcecode on GitHub instead of Google Code. Will ZIP files continue to be created at https://sourceforge.net/projects/tei/files/tei-oxygen/ ? If so, we'll need to edit this section of the wiki. Likewise if the directions for subscribing to the TEI framework have changed.

Kevin

On 3/13/15 5:10 AM, James Cummings wrote:

...
Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

Martin Holmes

11 a.m.

New subject: [tei-council] Fwd: Google Code shutting down

Copying Sebastian on this re TEIOO.

...

I agree that those two names are confusing, but I think "oxygen-tei" and "tei-oxygen" are still easily confused. It would be nice if we could come up with something even more distinctive.

I think the debian package is not so widely known or noticed as the oxygen-tei package -- unless you're installing TEI on a Debian-based system you wouldn't come across it. While we're looking at these downloads on SF, I think we should now remove TEIOO: http://sourceforge.net/projects/tei/files/ It hasn't been updated since 2009, and the Wiki page for it says that it's "now superceded by the transformations between TEI and OO in the general TEI stylesheets package (XSLT 2.0). This includes command-line scripts odttotei and teitoodt, is included in the OxGarage web service for TEI transformation, and is also available as a jar file for use in OpenOffice.org." http://wiki.tei-c.org/index.php/TEI_OpenOffice_Package I'm not sure what that last reference to a jar file actually means; if it refers to the TEIOO download (which consists of one jar for P5 and one for P4), then it appears to be saying that it's been superseded partly by itself. Cheers, Martin On 15-03-21 09:29 AM, Kevin Hawkins wrote:

...

I agree that those two names are confusing, but I think "oxygen-tei" and "tei-oxygen" are still easily confused. It would be nice if we could come up with something even more distinctive.

In any case, I don't have an opinion on renaming before or after the next P5 release.

K.

On 3/21/15 11:24 AM, Martin Holmes wrote:

...
Hi Kevin,

Instructions for subscribing should not change as a result of the move to GitHub, but we have agreed that we'll re-title the project "oxygen-tei" instead of "tei-oxygen" because the former is the name of the project on its repo, and the latter is already in use as the name of a deb package.

Whether we do this before or after the next P5 release hasn't been decided. What do we think?

Cheers, Martin

On 15-03-20 09:10 PM, Kevin Hawkins wrote:

...
I've updated http://wiki.tei-c.org/index.php/OXygen#Support_for_TEI to point to the sourcecode on GitHub instead of Google Code. Will ZIP files continue to be created at https://sourceforge.net/projects/tei/files/tei-oxygen/ ? If so, we'll need to edit this section of the wiki. Likewise if the directions for subscribing to the TEI framework have changed.

Kevin

On 3/13/15 5:10 AM, James Cummings wrote:

...
Sebastian is attempting to migrate this to github as we speak. Strangely, google code is experiencing a high level of demand.

-J

On 13/03/15 01:29, Hugh Cayless wrote:

...
This affects the TEI Oxygen framework. GitHub anyone?

Sent from my phone.

Begin forwarded message:

...
From: google-code-noreply@google.com Date: March 12, 2015 at 21:07:34 EDT To: philomousos@gmail.com Subject: Google Code shutting down Reply-To: google-code-noreply@google.com

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.

epidoc 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 google-code-shutdown@google.com.

-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.

3566

Age (days ago)

3574

Last active (days ago)

List overview

Download

10 comments

7 participants

participants (7)

Fabio Ciotti
Hugh Cayless
James Cummings
James Cummings
Kevin Hawkins
Martin Holmes
Peter Stadler