Comments on: Why just one DVCS? http://blogs.gnome.org/juanje/2008/12/14/why-just-one-dvcs/ Juanje's thoughts about GNOME, FLOSS and more Thu, 24 Sep 2009 08:14:18 +0000 http://wordpress.org/?v=2.8.5.2 hourly 1 By: juanje http://blogs.gnome.org/juanje/2008/12/14/why-just-one-dvcs/comment-page-1/#comment-15 juanje Sun, 14 Dec 2008 19:31:02 +0000 http://blogs.gnome.org/juanje/?p=35#comment-15 Pascal: Yes, you're right, but I think the most of the advantages come from the local thing of those systems, so doesn't really matters so much how you store and serve the code plus the metadata. The only thing that matters is you can use your local branches and comunucate with upstream with no troubles. Marko: Yes, of course, but I think those VCSs spend too much time to be differents and "the best", than to be compatibles and maybe that could be the point. If the VCSs are compatibles, you don't need maintain 3 mirros of the same code and almost the same metadata, converting all the time and checking those conversions.... (which is what actuallly can make harder the sysadmin work...). We'll just have one system and we serve the code and the metadata in one single place, but people can still use git, hg, bzr or whatever this layer support. Pascal: Yes, you’re right, but I think the most of the advantages come from the local thing of those systems, so doesn’t really matters so much how you store and serve the code plus the metadata. The only thing that matters is you can use your local branches and comunucate with upstream with no troubles.

Marko: Yes, of course, but I think those VCSs spend too much time to be differents and “the best”, than to be compatibles and maybe that could be the point. If the VCSs are compatibles, you don’t need maintain 3 mirros of the same code and almost the same metadata, converting all the time and checking those conversions…. (which is what actuallly can make harder the sysadmin work…). We’ll just have one system and we serve the code and the metadata in one single place, but people can still use git, hg, bzr or whatever this layer support.

]]> By: Marko Anastasov http://blogs.gnome.org/juanje/2008/12/14/why-just-one-dvcs/comment-page-1/#comment-13 Marko Anastasov Sun, 14 Dec 2008 19:18:52 +0000 http://blogs.gnome.org/juanje/?p=35#comment-13 Different projects choose different VCS's and developers interacting with them obviously adapt. Being opinionated and not burdening people with unnecessary choices is a good thing, and GNOME as a project should make a decision to use one, just as Rails, Ubuntu etc did. Trying to please everybody in a huge community is not the way to go IMO. Not to mention the burden from the sysadmin point view. Different projects choose different VCS’s and developers interacting with them obviously adapt. Being opinionated and not burdening people with unnecessary choices is a good thing, and GNOME as a project should make a decision to use one, just as Rails, Ubuntu etc did. Trying to please everybody in a huge community is not the way to go IMO. Not to mention the burden from the sysadmin point view.

]]> By: Pascal http://blogs.gnome.org/juanje/2008/12/14/why-just-one-dvcs/comment-page-1/#comment-12 Pascal Sun, 14 Dec 2008 18:59:19 +0000 http://blogs.gnome.org/juanje/?p=35#comment-12 Unfortunatly my experience about abstract interface is that you will lose the advantages of all the systems, and keep only what they can all manage. Unfortunatly my experience about abstract interface is that you will lose the advantages of all the systems, and keep only what they can all manage.

]]>