onetodo / cld2

Automatically exported from code.google.com/p/cld2
0 stars 0 forks source link

new code location? #35

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi, since google code is closing, where do you plan to move the packaging?

thanks!

Original issue reported on code.google.com by costamag...@gmail.com on 6 May 2015 at 2:21

GoogleCodeExporter commented 9 years ago
Most likely this will be migrated to GitHub, which is where a lot of the Google 
Code projects are moving.

Jason, are you going to do the export? I can help with the Chromium side of 
this, getting the repository address updated in the Chromium DEPS.

Original comment by andrewha...@google.com on 7 May 2015 at 10:14

GoogleCodeExporter commented 9 years ago
Yes, I have done this already for two other projects, and happy to do the CLD2 
export within the timeline we discussed (no later than June 1).

Original comment by ri...@google.com on 7 May 2015 at 3:08

GoogleCodeExporter commented 9 years ago
Have poked the Chromium team on what will be required to make this move, and I 
should note that the current repo is SVN based whereas GitHub (obviously) will 
be Git. Anyone downstream who is mirroring our repo would need to migrate from 
SVN to Git to continue receiving updates. I imagine that Git is widespread 
enough at this point for that not to be a major blocker for anyone.

Original comment by andrewha...@google.com on 7 May 2015 at 3:11

GoogleCodeExporter commented 9 years ago
I think it will be helpful to put a notice up shortly on the project homepage 
mentioning the impending move to GitHub. We'll can mention there any 
implications, such as migration from SVN to Git that would be required.

Original comment by ri...@google.com on 7 May 2015 at 3:24