Fwd: Google Code shutting down

[Jack O'Quin]

I recently got this notice from Google, saying that they will not much longer host these two UTexas ROS repositories.

- utexas-art-ros-pkg code for the autonomous vehicle, Marvin

- utexas-ros-pkg code belonging to the UTexas Learning Agents Research Group

Although Marvin has been retired, and the utexas-art-ros-pkg code is no longer actively maintained, there are still people who refer to it and ask questions.

So, I plan to follow their suggestion (below) of migrating the code to github, probably to a new group named austin-robot or utexas-art. Suggestions for other names or hosting options are welcome.

I will defer to Peter and Piyush to decide on utexas-ros-pkg. I no longer remember why I was an administrator for that repository.

---------- Forwarded message ----------
From: <google-co...@google.com>
Date: Thu, Mar 12, 2015 at 8:07 PM
Subject: Google Code shutting down
To: jack....@gmail.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.

• utexas-art-ros-pkg
• utexas-ros-pkg

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

--

 joq

[Michael Quinlan]

I think github with the same repo name makes the most sense for anybody who was previously referring to it.

--
You received this message because you are subscribed to the Google Groups "utexas-art-ros-pkg-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to utexas-art-ros-pkg...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jack O'Quin]

On Sat, Mar 14, 2015 at 2:51 PM, Michael Quinlan <michael...@gmail.com> wrote:

I think github with the same repo name makes the most sense for anybody who was previously referring to it.

Good idea. 

It will probably end up something like: austin-robot/utexas-art-ros-pkg.

--

 joq

[Piyush]

Hey Jack,

I highly recommend using https://github.com/nirvdrum/svn2git. It will
preserve the commit history. I've used it once before. I'm probably
gonna use it for the other repository that we have on code.google.

Piyush

[Jack O'Quin]

On Sat, Mar 14, 2015 at 5:34 PM, Piyush <piy...@gmail.com> wrote:

Hey Jack,

I highly recommend using https://github.com/nirvdrum/svn2git. It will
preserve the commit history. I've used it once before. I'm probably
gonna use it for the other repository that we have on code.google.

That automatic google code to github migration failed. Our repository was too big.

Today I migrated it by hand. The new repo is:

 * https://github.com/austin-robot/utexas-art-ros-pkg

If you want access, let me know. I don't plan to do much with it, except update the README and delete some stacks like velodyne that now live somewhere else.  

--

 joq