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.