<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Version Control Changes</title>
	<atom:link href="http://labs.creativecommons.org/2008/04/01/version-control-changes/feed/" rel="self" type="application/rss+xml" />
	<link>http://labs.creativecommons.org/2008/04/01/version-control-changes/</link>
	<description>by Creative Commons</description>
	<lastBuildDate>Mon, 17 Aug 2009 15:04:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: git-svn and svn:externals &#171; yergler.net</title>
		<link>http://labs.creativecommons.org/2008/04/01/version-control-changes/comment-page-1/#comment-1388</link>
		<dc:creator>git-svn and svn:externals &#171; yergler.net</dc:creator>
		<pubDate>Tue, 21 Jul 2009 16:47:27 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.creativecommons.org/2008/04/01/version-control-changes/#comment-1388</guid>
		<description>[...] Creative Commons we&#8217;re a dual-[D]VCS shop. Since we started self-hosting our repositories last year we&#8217;ve been using both Subversion and git. The rationale was pragmatic more than [...]</description>
		<content:encoded><![CDATA[<p>[...] Creative Commons we&#8217;re a dual-[D]VCS shop. Since we started self-hosting our repositories last year we&#8217;ve been using both Subversion and git. The rationale was pragmatic more than [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Issue Tracking at code.creativecommons.org - Creative Commons</title>
		<link>http://labs.creativecommons.org/2008/04/01/version-control-changes/comment-page-1/#comment-1040</link>
		<dc:creator>Issue Tracking at code.creativecommons.org - Creative Commons</dc:creator>
		<pubDate>Fri, 05 Sep 2008 21:19:40 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.creativecommons.org/2008/04/01/version-control-changes/#comment-1040</guid>
		<description>[...] the trend started when we moved our source repository, today we&#8217;re rolling out issue tracking on code.creativecommons.org. Our goals are two [...]</description>
		<content:encoded><![CDATA[<p>[...] the trend started when we moved our source repository, today we&#8217;re rolling out issue tracking on code.creativecommons.org. Our goals are two [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Narebski</title>
		<link>http://labs.creativecommons.org/2008/04/01/version-control-changes/comment-page-1/#comment-727</link>
		<dc:creator>Jakub Narebski</dc:creator>
		<pubDate>Sat, 05 Apr 2008 10:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.creativecommons.org/2008/04/01/version-control-changes/#comment-727</guid>
		<description>It looks like git web interface doesn&#039;t work (yet?), at least link at code.creativecommons.org named &quot;web view&quot; for Git, http://code.creativecommons.org/viewgit returns 404 Not Found error.</description>
		<content:encoded><![CDATA[<p>It looks like git web interface doesn&#8217;t work (yet?), at least link at code.creativecommons.org named &#8220;web view&#8221; for Git, <a href="http://code.creativecommons.org/viewgit" rel="nofollow">http://code.creativecommons.org/viewgit</a> returns 404 Not Found error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Hoersten</title>
		<link>http://labs.creativecommons.org/2008/04/01/version-control-changes/comment-page-1/#comment-718</link>
		<dc:creator>Luke Hoersten</dc:creator>
		<pubDate>Wed, 02 Apr 2008 18:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.creativecommons.org/2008/04/01/version-control-changes/#comment-718</guid>
		<description>Excellent move Nathan. It&#039;s never an easy call to move to a whole new revision control system/model when you have such a large code base (or in your case, large composition of code bases). When I worked on CC related stuff, it was definitely a hurtle to work with SVN and especially SF (which was constantly slow or down). VCSs should facilitate not hinder and I think DVCSs do that.

Git and DVCSs in general can be slightly more challenging for developers to learn, especially after being so used to CVS or SVN. For OS X users, there&#039;s an awesome GUI called GitNub hosted at GitHub. For learning DVCSs in general, here&#039;s a collection of resources, such as guides and tech talks. Linus&#039; tech talk is a must-see.

Good luck with the migration!</description>
		<content:encoded><![CDATA[<p>Excellent move Nathan. It&#8217;s never an easy call to move to a whole new revision control system/model when you have such a large code base (or in your case, large composition of code bases). When I worked on CC related stuff, it was definitely a hurtle to work with SVN and especially SF (which was constantly slow or down). VCSs should facilitate not hinder and I think DVCSs do that.</p>
<p>Git and DVCSs in general can be slightly more challenging for developers to learn, especially after being so used to CVS or SVN. For OS X users, there&#8217;s an awesome GUI called GitNub hosted at GitHub. For learning DVCSs in general, here&#8217;s a collection of resources, such as guides and tech talks. Linus&#8217; tech talk is a must-see.</p>
<p>Good luck with the migration!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
