<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Moxune &#187; git</title>
	<atom:link href="http://moxune.com/tags/git/feed/" rel="self" type="application/rss+xml" />
	<link>http://moxune.com</link>
	<description>&#34;Tech Moxy&#34; ~ Moxune is the Surgical Team most capable of delivering your next complex PHP Application on time &#38; under budget.</description>
	<lastBuildDate>Thu, 18 Oct 2012 00:29:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Managing customizations to an evolving third-party product</title>
		<link>http://moxune.com/blog/2011/05/managing-customizations-to-an-evolving-third-party-product/</link>
		<comments>http://moxune.com/blog/2011/05/managing-customizations-to-an-evolving-third-party-product/#comments</comments>
		<pubDate>Wed, 11 May 2011 15:55:30 +0000</pubDate>
		<dc:creator>Nathan Nobbe</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[Version Control]]></category>

		<guid isPermaLink="false">http://moxune.com/?p=291</guid>
		<description><![CDATA[Your Product Like many projects these days, there&#8217;s no need to build completely from scratch. Off-the-shelf Open Source applications like... <a href="http://moxune.com/blog/2011/05/managing-customizations-to-an-evolving-third-party-product/">More &#187;</a>]]></description>
			<content:encoded><![CDATA[Your Product
Like many projects these days, there's no need to build completely from scratch.  Off-the-shelf Open Source applications like WordPress, have changed the landscape.  Another situation we encountered with a client once was a code generat]]></content:encoded>
			<wfw:commentRss>http://moxune.com/blog/2011/05/managing-customizations-to-an-evolving-third-party-product/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t get stuck with an unparseable gitosis.conf</title>
		<link>http://moxune.com/blog/2011/04/prevent-commit-of-unparseable-gitosis-conf-file/</link>
		<comments>http://moxune.com/blog/2011/04/prevent-commit-of-unparseable-gitosis-conf-file/#comments</comments>
		<pubDate>Mon, 11 Apr 2011 20:02:33 +0000</pubDate>
		<dc:creator>Nathan Nobbe</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[gitosis]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[system administration]]></category>

		<guid isPermaLink="false">http://staging.moxune.net/?p=170</guid>
		<description><![CDATA[Getting started with gitosis So you've evaluated the SaaS landscape the Web has to offer and decided to go it... <a href="http://moxune.com/blog/2011/04/prevent-commit-of-unparseable-gitosis-conf-file/">More &#187;</a>]]></description>
			<content:encoded><![CDATA[Getting started with gitosis
So you've evaluated the SaaS landscape the Web has to offer and decided to go it alone and host public repositories behind your corporate firewall.  You've also decided you want to build the service using free components]]></content:encoded>
			<wfw:commentRss>http://moxune.com/blog/2011/04/prevent-commit-of-unparseable-gitosis-conf-file/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
