Re: [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