Hello, all, fwiw: Where I work, we use GitHub for projects considerably smaller than wsjt. We are quite pleased with it. These days, GitHub is the obvious thing to do at least in the part of the software developing community where I hang out.
Porting things from svn to git should be easy. There exists well-reputed tooling for this task. I've served as SVN and as Git admin in projects considerably larger than wsjt, but have not done a port from SVN to Git yet. I've always wanted to play around with that tooling. So, if the project decides it is at least mildly interested in the Git way, I'd volunteer to port the SVN repo to Git (host it on my own server for starters), so you folks can have a look. Throw it away if you don't like it, or take it if you do. Regards, Andreas DJ3EI Am 18.02.2014 03:30, schrieb Greg Beam: > Hello All, > > I replied to this earlier, thought I had sent it too the list, but > went back to Joe only. > > Link to Open Source Hosting facilities, comparing features, popularity > and such: > > http://en.wikipedia.org/wiki/Comparison_of_open-source_software_hosting_facilities > > My recommendations would be, in order of preference: > > * Launchpad > * Google Code > * GNU Savannah > * GitHub > * Gitorious > > All of these are well supported, provide a range of free tools and > should work well for WSJT projects. > > Personally, I like Launchpad for it's versatile work flows, tools > integration (bugs, blueprints, Q&A, Translations, etc.) > > Google Code would be next with Savannah a very close second. Git is ok > for really large projects which need or want true distributed > work-flows. I think it's overkill for smaller projects. > > > 73's > Greg, KI7MT > [email protected] > > > On 2/17/2014 20:47, Charles Yahrling wrote: > > Since I never heard of subversion until a few weeks a go I am the > > least qualified to make any recommendation. But a quick search on > > "alternatives to sourceforge" popped up a canned search by the time > > I got to the c. So it seems a lot of others are in the same boat. > > Have you considered Google Code Hosting, which is free for svn and > > mercurial?. At the site Alternativeto.net it was the highest > > ranking of free svn sites. Only two ranked higher overall but they > > only supported git, or git and mercurial Some people love to hate > > google but if reliability is key they would seem to be a good bet. > > From the site: > > > Host open-source software projects using Subversion or Mercurial > > for revision control. Google Code also includes a wiki for > > documentation, issue tracking and file download feature. It is free > > for Open Source projects that are licensed under one of nine > > licenses (Apache, Artistic, BSD, GPLv2, GPLv3, LGPL, MIT, MPL and > > EPL). > > > $0.02 chuck kb1zmx > > > > On Mon, Feb 17, 2014 at 8:05 PM, Joe Taylor <[email protected]> > > wrote: > > >> Hi all, > >> > >> 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? > >> > >> -- 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 > > _______________________________________________ > 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
