Google Code closing, moving the repository?

8 views
Skip to first unread message

jerome

unread,
Apr 21, 2015, 4:49:27 PM4/21/15
to gp...@googlegroups.com
Hi,

As Google Code will be closing soon, I gave a try at the button "Export to GitHub". But actually it's a pain in the a**. The code is exported correctly but else:
  • The export function doesn't move the wiki properly (its somewhere in a branch, although GitHub offers a wiki and the history is gone).
  • There are too much things on the Github user interface. Google Code was way simpler and better!
  • Github make it complicated in forcing to use git instead of svn for all projects.
  • The Contributors aren't automatically moved.
  • And the download seems to have been ignored completely.
Has anyone experience with moving Google Code projects to other platforms than GitHub?

OK, there weren't much going on on gpsvp during the last years. I still have a WM phone somewhere in a drawer, but ok I'm not using it anymore. But I'm still using gpsvp on my PC! That's why I would like to keep a usable repository for gpsvp.

Regards
Jerome

Mihai Stanescu

unread,
Apr 22, 2015, 1:51:59 AM4/22/15
to gp...@googlegroups.com

Hi

"Github make it complicated in forcing to use git instead of svn for all projects".

i would consider this the best thing that happened to svn.
Git is so much supperior.

Mihai

--
You received this message because you are subscribed to the Google Groups "gpsVP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gpsvp+un...@googlegroups.com.
To post to this group, send email to gp...@googlegroups.com.
Visit this group at http://groups.google.com/group/gpsvp.
For more options, visit https://groups.google.com/d/optout.

Jerome

unread,
Apr 22, 2015, 3:52:20 PM4/22/15
to gp...@googlegroups.com
Hi,

Not in my opinion. It's true that git has some advantages (merging works much better, you can have a complete copy of the repository....) but it also has some disadvantages (It much more complicated to use, you must have a whole copy of the repository, the history is not to clear, the revision numbers aren't made for humans...).
And for a small project without a lot of active contributors, svn ist better suited in my opinion. Especially the steep learning curve of git is not a good thing to get new contributors.

Jerome
Reply all
Reply to author
Forward
0 new messages