Hi, With the recent problems we had and still have with Sourceforge, I've decided to move our repository to osdn.net. The TortoiseSVN project is already set up there, and the people at osdn.net are very helpful and are already working on importing my backup of the TSVN repository. But since the repo dump is 14GB in size, that will take a few hours at least. In the mean time, all of you with commit access please create an account on osdn.net and email me (or post it here) your account name so I can give you commit access there.
The reason I've decided to move away from Sourceforge is not only the repeated outages and other problems, it's also on how SF handles the problems and communicates about it: - The status page is a joke: no real info about the problems, but it's still referred to as the go-to page when looking for info about outages: https://sourceforge.net/blog/category/sitestatus/ - Even the twitter account doesn't provide useful information. The last tweet tells that all is working now again - which is not true since shell access still doesn't work! - Getting help from SF staff is impossible - all you get are predefined answers which don't help at all. - Shell access still isn't working, and hasn't been for more than three weeks now. That's unacceptable: without that I can't try fixing the corrupted repo, and I can't replace it with my backup either. - They mentioned a DOS attack as the reason for the last outage, which I highly doubt is true. Because a DOS attack that lasts more than a week would have been mentioned all over the internet since it would by definition also affect all routers that connect in any way to SF. It seems to me they simply didn't configure the new datacenter setup correctly and couldn't handle the normal traffic they got before. - The default answer to all issues opened about shell access not working is "Our development and devops teams are continuing to work together to resolve all issues after a recent datacenter migration as quickly as possible. As of right now, we do not have an official ETA when this will be fixed." Which seems to me as if they moved without having set up everything at the new data center and just assumed they could do that after the move. - The first thing that worked after the outage was the front page with lots of ads - only three (!!) days later the rest started slowly working again. Which clearly shows where their priorities are. So, the first step will be to get the repository backup up and running on osdn.net. And give the committers access to it again. Then once that's working, with the next release we'll move our downloads there as well. After that I'll mark the project on SF as inactive and redirect to our homepage. Forum posts/mailing lists are kept here. I don't think we should move those to osdn.net. Sorry for not consulting with you guys first about the move, but there are not many options available for hosting svn repositories... Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/f7677905-2aa2-411c-a071-3350adf69ac6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
