I'm not sure I've ever posted on this list, but I do follow along since I am interested in wsjt development. One thing I believe is very important is the preservation of code history. It's one of the reasons people use a source code management system. I know with svn it is possible to create an archive of the entire repository so that it can be easily moved to another system with all branches and checkin history intact. I've forgotten the exact details of this operation since I haven't been responsible for such an operation in many years.

Anyway, I hope that BerliOS will support such a transition to SourceForge. I would hate for the migration to be a simple checkout of top of tree and then starting over on SourceForge.

John

On 2/18/2014 2:53 PM, Joe Taylor wrote:
Thanks to all for the input and suggestions on a new project hosting service -- and for the offers of help.

I understand the comparisons between git and svn, and also some of the advantages/disadvantages of various possible sites, including

 GitHub       (most features are git-oriented; no mailing list support)
 Gitorious    (          "                   )
 GNU Savannah (doesn't allow "non-free" requirements, like our kvasd)
 Google Code  (doesn't support mailman)
 Launchpad    (doesn't support svn)
 SourceForge  (ugly pages, advertising, etc...)

I've used git -- it's a good system. On balance, though, I think our path of least resistance (and least disruption) is to stick with Subversion as our base repository. Individuals can always use git locally, and I imagine some already do.

SourceForge seems to meet all our needs and will supposedly migrate our whole project seamlessly. I'm inclined to ask them to do this, and see how we like it. If all seems well, we can then decide to move all subsequent work there.

Questions:

1. Any objections or further appeals to reason? :-)

2. When to do this?

3. Bill, would you prefer to commit your big changes to WSJT-X first? Or perhaps to make a branch, and commit your new code to that?

    -- Joe, K1JT
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

Reply via email to