Revision: 1292
Author: mr0...@mro.name
Date: Sun Aug 9 23:02:11 2015 UTC
Log: Edited wiki page RepositoryMigration through web user interface.
https://code.google.com/p/piccolo2d/source/detail?r=1292
Modified:
/wiki/RepositoryMigration.wiki
=======================================
--- /wiki/RepositoryMigration.wiki Fri Aug 7 22:55:28 2015 UTC
+++ /wiki/RepositoryMigration.wiki Sun Aug 9 23:02:11 2015 UTC
@@ -6,61 +6,4 @@
----------
*!!! REMINDER !!!* Google Code will become read-only on August 25th and I
guess it will remain so afterwards. That's little more than two weeks from
now.
-As far as I see, there's NO LOSSLESS migration procedure yet due to the
non-standard svn directory layout (branches/tags/trunk per sub-projects
piccolo2d.java piccolo2d.net pocketpiccolo each).
-
-I wouldn't mind loosing all but java, So I may do an export to github of
the java part only. Also I will not care about history nor issue tracker
nor wiki pages if that takes extra effort.
-
-If anybody (YOU!) wants to see a more comprehensive migration, please
don't expect anybody else to care for it. Give noise and help.
-----------
-
-The following is a quick brain.dump of mine - *please edit & comment
recklessly* without asking. In case it's all versioned. Still.
-
-= Goals =
-
-the following may not all be of equal importance, nor be in any order:
-
- # keep history (code)
- # keep authorship per line a.k.a. blame/praise (code)
- # keep history (website)
- # keep authorship per line a.k.a. blame/praise (website)
- # clean up author names (e.g. I used at least 3 different ones during
the years) {{{$ svn log --xml http://piccolo2d.googlecode.com/svn/ | grep
author | sort -u | perl -pe 's/.*>(.*?)<.*/$1 = /'}}}
- # keep & update wiki pages
- # keep open issues
- # keep closed issues
- # keep issue-revision relations
- # split into per-language repositories
- # other tweaks as in
http://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git#Subversion
-
-= Hosting =
-
-ranging from
-
- # hosted (until hoster shuts down) (e.g. github, bitbucket, source
forge, etc.)
- # hosted with option to move to self-hosting (e.g. [http://gitlab.org
gitlab])
- # self hosted ([http://fossil-scm.org/ fossil], gitlab, gitolite, ?)
-
-= SCM =
-
- # git
- # mercurial
- # [http://fossil-scm.org/ fossil]
- # ?
-
-== Mirrors (Unofficial) ==
-
- # https://github.com/mro the following keep history, but drop issues.
Naively via {{{$ git svn clone http://piccolo2d.googlecode.com/svn/<repo>/
-s}}}
- # https://github.com/mro/piccolo2d.site
- # https://github.com/mro/piccolo2d.java
- # https://github.com/mro/piccolo2d.net
- # https://github.com/mro/pocketpiccolo2d.net
- # https://github.com/search?utf8=%E2%9C%93&q=piccolo2d
-
-== Discussion ==
-
-I'm confused, there's already a piccolo2d organizational account?
-
-> *@mro*: the owner was so kind to invite us into
https://github.com/piccolo2d. So we _could_ use it to migrate the code to,
if we want.
-
-My most important concern is that contributions make it across the
migration; specifically that user ids from Google Code match up with user
ids in Github. It looks to me like that didn't work for the migration that
resulted in this repo https://github.com/piccolo2d/piccolo2d.java
-
-> *@mro*: ids usually won't match out-of-the-box, so we'll ask/spy round
which github ids to use and map them once finally migrating. (see 'clean up
author names' above). So I would recommend to re-create the git repos.
*@sam*, your repos look nice, how did you export svn to git? How did you
manage to keep the issues?
+See https://github.com/piccolo2d/google2github
--
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
---
You received this message because you are subscribed to the Google Groups "Piccolo2D Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to piccolo2d-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
