[rfk-dev] Moving off SourceForge

Peter A. H. Peterson pedro at tastytronic.net
Wed Oct 31 08:48:51 PDT 2012

Quoting Eric S. Raymond:
> There has been some talk of moving the project off SourceForge.
> On reflection, I don't think I understand why.  In what respects
> does SourceForge seem to be a bad fit?

There's no great pressure to do so.

My motivation for doing so is that since most of the activity happens
on rfk.org, and we archive source code there as a record of all
rfkiana, sourceforge tends to become a bit forgotten. It's also a
dependency on the project that generally serves little purpose other
than providing CVS. We forget our logins and then must go through
recovery processes. We have to wait 5 seconds to download tarballs
while looking at ads.

On the other hand, by setting up a community rcs at rfk.org, we keep
everything under one roof, in one place. It's just cleaner and
streamlines the processes of updating code and/or including new ports.

But I don't think that the migration process -- whatever ends up
happening -- should delay a release. It's definitely a secondary goal.

I've been thinking about setting up Gitolite:


It seems like it meets the needs of giving some finer grained access
to the git repo by SSH key, while not providing shell access to every
developer. It's also pretty lightweight.


Peter A. H. Peterson
Graduate Student Researcher
Laboratory for Advanced Systems Research
University of California, Los Angeles

More information about the rfk-dev mailing list