[0:52:40] "It is incredible how stupid these people are"
Status: Abandoned
Brought to you by:
mdbesten
Menu
▾
▴
This is an good question, it is true when we open Sourceforge we notice that the SCM tool is SVN, but here's a link that shows that Sourceforge supports Git and other SCM:
https://sourceforge.net/apps/trac/sourceforge/wiki/What%20is%20Source%20Code%20Management
but why ? i think it is a question of centralization... and more control
what do you think?
good question, a quick search on google doesn't give any answer or hint... Any ideas guys?
Maybe it's because SVN was developped in 2000 and Git in 2005. Also people prefer to develop with SVN because they know it well
This is a consumer behavior topic. I think the answer could be that people have habits. They are getting use to the things they use for a long time, and in this case if the system is successful they won't risk at doing something else.
The change will be considered only if they would see a malfunction or loss.
Paul David has written on the issue of getting stuck with a particular technology: "Clio and the economics of QWERTY - see http://www.jstor.org/pss/1805621 - but note that Linus also makes some comments on sourceforge himself at the end of his talk.
indeed he says that sourceforge missed the point when focusing on performance for branching, and adds that's not the thing they should be focusing on, but on merging however they certainly have other things they are proud of haven't they? it might be that SVN isn't that bad at all in the end, but I doubt we can discuss this point without using it...
j'ai trouvé des articles qui parlent de l'utilisation de Git en local, et SVN comme serveur central ce qui permet de passer vers Git pas à pas, sans perdre le control...
Je trouve que c'est très intelligent d'essayer de profiter des points forts de Git dans la distribution et des points forts de SVN dans la centralisation...
http://blog.courtine.org/2010/10/12/allons-un-peu-plus-loin-avec-git-svn/