I propose migrating the uim upstream repository from Subversion to Git.

I created the following git repository in GitHub for personal use:
https://github.com/mnogu/uim
I'm using git-svn and this GitHub repository to develop uim
and I feel more comfortable than using Subversion directly,
but it is complicated to operate both the upstream repository and the
GitHub repository above.
So I want the upstream repository to be migrated to Git.

These are the advantages of Git over Subversion.

1. offline operations
Some operations, such as viewing logs and committing, are faster
because we can perform these operations offline.

2. private branch
We can create a private branch to commit work-in-progress or
experimental codes without committing to a upstream repository.

3. non-committer
Non-committers can easily modify codes and follow changes in the
upstream repository. This makes it easier for non-committers to
contribute uim. The more contributors, the better.

We have some scripts which depends on Subversion and we have to
rewrite the scripts when migrating to Git, but IMO, we will gain large
benefits after migrating to Git.

Any comments?

Also with migrating to git, I think it good timing for you to take a
maintainer role of uim.
I think you are the most active developer introducing new things and
implementations to
uim currently.  Of course I can help you to some extent.  Could you
consider to become a
maintainer?

Sorry for the late reply.

(12/02/20 13:54), Etsushi Kato wrote:

Changes to doc/RELEASING would be as follows:

     svn export http://uim.googlecode.com/svn/trunk
     -> git archive --remote=<url of uim repo> HEAD | tar -xvf -

     svn cp https://uim.googlecode.com/svn/trunk \
            https://uim.googlecode.com/svn/branches/x.y
     -> git branch x.y && git push origin x.y

     svn cp https://uim.googlecode.com/svn/branches/x.y \
            https://uim.googlecode.com/svn/tags/uim-x.y.z-alpha
     -> git tag -a uim-x.y.z-alpha && git push --tags

     svn export http://uim.googlecode.com/svn/tags/uim-x.y.z-alpha
     -> git archive --remote=<url of uim repo> uim-x.y.z-alpha | tar -xvf -

Changes to sigscheme/doc/release.txt would be similar to ones to
doc/RELEASING.

FYI, My migration plan is as follows:

(1) Convert repositories
Convert 3 repositories from Subversion to Git with svn2git.

* uim
* sigscheme
* libgcroots

(2) Add libgcroots as a submodule to sigscheme

git submodule add <url of libgcroots repo>

(3) Add sigscheme as a submodule to uim

git submodule add <url of sigscheme repo>

(4) Replace `svn co' in make-wc.sh with `git submodule'

* svn export $SSCM_URL sigscheme
* svn export $LIBGCROOTS_URL sigscheme/libgcroots
-> git submodule update --init --recursive

(5) Replace `svn export' in make-dist.sh with `git submodule'

In the uim repository,
* svn export $SSCM_URL sigscheme
* svn export $LIBGCROOTS_URL sigscheme/libgcroots
-> git submodule update --init --recursive

In the sigscheme repository,
* svn export $LIBGCROOTS_URL libgcroots
-> git submodule update --init

(6) Update tools/gnuify-changelog.pl to handle `git log'

See https://gist.github.com/1892559

(7) Replace `svn log' in Makefile.am with `git log'

svn log $(RELEASE_URL) | ./gnuify-changelog.pl > $@
-> git log $(RELEASE_URL) | ./gnuify-changelog.pl > $@

(8) Replace `svn export' in Makefile.am with `git archive'

svn export $(UIM_REPOSITORY)/trunk/tools/gnuify-changelog.pl
-> git archive --remote=<url of uim repo> HEAD tools/gnuify-changelog.pl
-o gnuify-changelog.pl

(9) Update RELEASING and sigscheme/doc/release.txt

I will create a converted Git repository in Google Code
instead of GitHub because no all committer has a GitHub account.
If there is no objection from the contributors,
I will carry out the migration plan this weekend.