googlecode repo locked

[Amelia A Lewis]

Heyo.

We are beginning the move to github. I'll send out details when it's
completed (at which point we'll ask everyone to do a pull into a new
workspace).

No changes committed after noon eastern time today will be copied to
the new repo. I can't actually lock the repo down (except by dropping
access for everyone, which seems needless), but that's where we are
right now.

Expect an update in a few hours.

Amy!
--
aal, et alia, et alii

[Amelia A Lewis]

Following up:

The source code for genxdm has been relocated to a TIBCO-hosted repo at
github:

https://github.com/TIBCOSoftware/genxdm

To establish your own complete local working copy, do this with the
command-line client:

git clone https://github.com/TIBCOSoftware/genxdm.git

This will create a local directory called genxdm, containing the
project and eclipse top-level directories (formerly found in
genxdm.googlecode.com/svn/trunk/project and
genxdm.googlecode.com/svn/trunk/eclipse), containing the 'master'
branch. git remote -v will show you the origin (similar to svn info).
That should get folks started; if you're not familiar with git, you
will be pretty soon, huh?

Issues and wiki have *not* been transferred as yet. Please consider the
old and new repos still locked (but feel free to check out the new
repo, just don't make any commits, 'kay?).

Amy!

[Amelia A Lewis]

Looks like this is going to take a while. The issue exporter is
supposed to be rate limited, to avoid triggering github's
abuse-prevention limits, but it failed anyway. So ... we wait a while,
then try again (possibly it triggered because this was too soon after
repo population?).

Still locked. Please don't make changes until notified. Thanks.

Amy!

[Amelia A Lewis]

Hey.

Consider the old repo deprecated. I'm going to have to examine how to
do various things in github, but we can *build* from the code base
that's there. Also, I removed all the downloads except for the last one
that's there; I want to remove that one, too, but I'll wait a tick and
check with folks on winding up our googlecode presence rather than
being unilateral.

Do *not* modify issues in github yet. As a matter of fact, while you
are encouraged to check out working copies, please do not make *any*
changes in github yet, okay? Thanks for your help and your patience.

The issue is that the issues importer is rate limited. I can transfer
around eight issues at a time, and then have to wait an hour to try
again. It's relatively easy to wait more than an hour, but I still only
get eight issues in the next slot. Waiting less than an hour reduces
the number. So far I've transferred thirty of one hundred sixty-two
issues. If I keep doing this every hour that I remember, it's still
fourteen hours. Better to say that it's fourteen updates, which can
occur at a minimum interval of one hour. In other words, if I keep
doing stuff tonight, on and off, and all day tomorrow, then we might be
done by Wednesday morning. Which is what I'll shoot for. I've got the
wiki/markdown stuff that can be committed, too, already modified.
Sadly, it works off a Google Takeout archive and a personal
authorization token that github generates, so it's not a task easily
shared, either. It's unfortunate that google and github couldn't have
worked this out to run more cleanly.

More of a pain in the butt than I expected. Oh, well. We're getting
there; it just takes time. If the rate-limiting in the issues importer
actually worked, we might be able to make slow-steady progress, instead
of doing it in bursts and getting throttled.

Amy!