Kochief news and repo question
Gabriel Farrell
kochief.org, which is on my Linode VPS. I migrated the front page of
http://code.google.com/p/fac-back-opac/ over, and I plan to clean it
up and reorganize a bit. I'll leave the registration there open for a
few days for anyone who wishes to sign up.
The todo list for further migration is now:
1. Move the repository
2. Move the Google group
As for the repository, I've already got
http://code.google.com/p/kochief/ and I can sync the current repo to
that at any point. Then I'll need to point the repo at the server
where kochief.org sits to the new location (needs to be local for
Trac). While I'm at it, I could change up my setup [1] to take
advantage of the new post-commit web hooks feature [2].
The recent announcement about Python [3], however, got me thinking
that I should be looking to move to Hg as long as we're moving anyway.
I went ahead and started http://bitbucket.org/gsf/kochief/ over at
bitbucket.org to check that out. I find it annoying that the project
URL includes my name, and would probably set up a team_kochief user or
something for the official site if we were to use Bitbucket. The
issue tracker (with hooks into the repo) and wiki are pretty nice,
too, so we could just host the whole thing over there. We could even
apply for an account with a CNAME (maybe free if they like the
project).
On the third hand, it wouldn't be hard to set up an Hg repo on the
kochief.org machine. I'd like to stick with Trac if possible, because
I'm so familiar with it. There's an Hg plugin for Trac [4], but I'm
worried about some of the issues mentioned there.
The last but not least option is I could just host the SVN repo on the
kochief.org machine. It would really simplify things, and it would
look good for everything to be located at the same place (except the
mailing list, which I'm fine with leaving at Google). The drawback is
that when that machine goes down, nothing is available, but the repo
at Google hasn't always been available, and I feel pretty good about
the care and feeding of it after 4+ years of doing so (and I do
incremental backups). Also, the repo could be mirrored to Google Code
or Bitbucket or wherever. The other drawback, of course, is that it
would be so 20th century, so unDistributed Version Control.
Apologies for the length. I'm really open to any of these options at
this point. Feedback much appreciated.
[1] http://rc98.net/googsvnsync
[2] http://code.google.com/p/support/wiki/PostCommitWebHooks
[3] http://mail.python.org/pipermail/python-dev/2009-March/087931.html
[4] http://trac.edgewall.org/wiki/TracMercurial
Ed Summers
//Ed
Dan Scott
<snip>
> The last but not least option is I could just host the SVN repo on the
> kochief.org machine. It would really simplify things, and it would
> look good for everything to be located at the same place (except the
> mailing list, which I'm fine with leaving at Google). The drawback is
> that when that machine goes down, nothing is available, but the repo
> at Google hasn't always been available, and I feel pretty good about
> the care and feeding of it after 4+ years of doing so (and I do
> incremental backups). Also, the repo could be mirrored to Google Code
> or Bitbucket or wherever. The other drawback, of course, is that it
> would be so 20th century, so unDistributed Version Control.
I'm VCS-neutral. bzr, Hg, git - they all have bridges to SVN.
I have full confidence in Gabe's admin capabilities, and will go where
ever I need, with whatever tools are required, to follow the Kochief.
--
Dan Scott
Laurentian University
Gabriel Farrell
Kochief front. I picked up kochief.org so I moved the Trac instance
there from trac.rc98.net/fbo. I'm more used to Trac than the
offerings at Google, but I could be swayed to just set up kochief.org
as a pointer to http://code.google.com/p/kochief/ and do the wiki,
issues, etc. there.
Ross Singer
use Google Code's SVN repo?
-Ross.
Gabriel Farrell
needs a local repo.
But now that Ed's raised doubts (thanks :)), I am thinking it would be
best to keep everything at http://code.google.com/p/kochief/. The big
gain in the near term is user management -- it was super easy to copy
and paste everyone from fac-back-opac to kochief, and it's no fun
trying to keep that in sync between Google and the Trac. And in the
long term I of course don't have to be responsible for maintenance.
The issue tracking at Google really isn't that bad, I just have to get
used to it.
Ed Summers
> But now that Ed's raised doubts (thanks :)), I am thinking it would be
> best to keep everything at http://code.google.com/p/kochief/. The big
> gain in the near term is user management -- it was super easy to copy
> and paste everyone from fac-back-opac to kochief, and it's no fun
> trying to keep that in sync between Google and the Trac. And in the
> long term I of course don't have to be responsible for maintenance.
> The issue tracking at Google really isn't that bad, I just have to get
> used to it.
Cool, sorry to rain on the parade Gabe. I like the idea of having a
shiny domain for kochief ... but I think you hit the nail on the head
with the user management part.
//Ed
Gabriel Farrell
https://kochief.googlecode.com/svn now. I'll direct people to
http://kochief.googlecode.com from both
http://fac-back-opac.googlecode.com and http://kochief.org, and we'll
handle issue tracking and all the rest there. kochief.org will still
be the place for snazzy graphics.
Gabriel Farrell
http://kochief.googlecode.com/, the official site for code and
development of Kochief. I've started a new Google Group because I was
unable to just move the Fac-Back-OPAC group. Y'all should have
received invitations. Any new discussions should start at
http://groups.google.com/group/kochief