On 17/02/2014 20:05, Joe Taylor wrote:
Hi all,
Hi Joe,

An impending issue for us to ponder:

BerliOS has announced that their hosting service for open-source projects like ours will end on April 30 of this year.

We must consider the available options for moving the WSJT project elsewhere.

BerliOS is cooperating with SourceForge to (supposedly) make migration there relatively painless. I'm not a SourceForge fan -- there's far too much extraneous "noise" (read: Advertising) on their web pages, which anyway seem to me to be poorly designed and organized.

Nevertheless, SourceForge *may* be our best option. We don't use the repository web site as the place most users go for downloads -- I've always kept the WSJT Home Page elsewhere, and it has no annoying pollution from advertising. Those of us who contribute to source code and documentation use the repository almost entitrely for checkouts and commits, so we seldom need to look at the web pages. In that case, SourceForge may not be too objectionable.

With that said, I'm certainly not an expert on these things. Does anyone know of an alternative to SourceForge that might be better?
Any other opinions or advice?
The SourceForge migration does look attractive since it is the recommended path and has tools in place to migrate the whole site. There are fairly simple instructions for moving the individual components to other hosts so other destinations are relatively easy too. One of the most important aspects is the migration of the mailing lists so a host that uses 'mailman' is important; making the migration of the ML archives trivial.

SourceForge does have some very popular projects on board which might increase its lifespan.

I see some are suggesting a switch to a different VCS, this too has merits and git certainly has many advantages over Subversion. I would not recommend a switch in VCS at the same time as a switch in project host, Subversion is easier to understand and use than git and developers who wish to can use git locally using the git-svn tools without having to migrate the whole VCS for everyone. The biggest advantage of a simple switch to another Subversion host is that work in progress can be switched (svn relocate) easily to the new repository whereas a VCS switch would require all developers to check in all outstanding work in a coordinated fashion or face a complex migration of their work in progress.
    -- Joe, K1JT
Just my 2p
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

Reply via email to