[Fxruby-announce] Re: Moving to RubyForge (was: Update: FXRuby 1.2a2 Status)
Status: Inactive
Brought to you by:
lyle
From: Lyle J. <ly...@kn...> - 2004-07-14 18:17:41
|
On Jul 14, 2004, at 10:24 AM, Curt Hibbs wrote: > You should really "bite the bullet" and move to RubyForge. These kind > of > problems seem all-too-common on SourceForge. You are correct that there are a number of flaws with SourceForge.net, and believe me that I'm very tempted to move the project to RubyForge. There are at least two potential problems with the current set of services provided by RubyForge. And I say "potential" because they may not really be problems, but they are things about which I am unclear. One concern is that SourceForge.net provides what they call "VHOST services" that allow the SourceForge.net web server to "answer" for my fxruby.org domain name. That is, when you visit: http://www.fxruby.org you're viewing paged hosted on their web servers. I would want this to work on RubyForge as well, and it may be that this is no big deal to get working (I have filed a support request about this). But I definitely don't want that URL (http://www.fxruby.org) to "break" as a result of the move. Another thing which bothers me, but which is not necessarily a problem, is the lack of shell account support at RubyForge. I can probably work around this, but there are numerous times when it has come in handy for my SourceForge.net project(s). |