<?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"
	>
<channel>
	<title>Comments on: Project Hosting on Google Code</title>
	<atom:link href="http://benramsey.com/archives/project-hosting-on-google-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://benramsey.com/archives/project-hosting-on-google-code/</link>
	<description>PHP and Other Techno-babble</description>
	<pubDate>Sat, 11 Oct 2008 14:10:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Andrew Chilton</title>
		<link>http://benramsey.com/archives/project-hosting-on-google-code/#comment-4518</link>
		<dc:creator>Andrew Chilton</dc:creator>
		<pubDate>Sat, 12 Aug 2006 05:13:33 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=156#comment-4518</guid>
		<description>Talking about the APIs, for me the most important part of it is already done - the Subversion repository gets you back all your code and it is already defined independently of Google.

It would be good to get all the Issue Tracker data though :) That's the other main part of the service from what I can see.</description>
		<content:encoded><![CDATA[<p>Talking about the APIs, for me the most important part of it is already done &#8211; the Subversion repository gets you back all your code and it is already defined independently of Google.</p>
<p>It would be good to get all the Issue Tracker data though <img src='http://benramsey.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> That&#8217;s the other main part of the service from what I can see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interessant OSCON spul &#124; Scriptorama</title>
		<link>http://benramsey.com/archives/project-hosting-on-google-code/#comment-4511</link>
		<dc:creator>Interessant OSCON spul &#124; Scriptorama</dc:creator>
		<pubDate>Wed, 09 Aug 2006 18:33:27 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=156#comment-4511</guid>
		<description>[...] Meer informatie kun je hier terugvinden. [...]</description>
		<content:encoded><![CDATA[<p>[...] Meer informatie kun je hier terugvinden. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Stein</title>
		<link>http://benramsey.com/archives/project-hosting-on-google-code/#comment-4487</link>
		<dc:creator>Greg Stein</dc:creator>
		<pubDate>Sat, 29 Jul 2006 05:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=156#comment-4487</guid>
		<description>We don't want to break people, and that is the heart of the problem. If we open an API, then we'd have to continue to support it no matter what. And what if that interferes with some new cool feature that we'd like to do? Eek.

Don't get me wrong... I'd like to have APIs, but we'll do it carefully so that we retain something very simple that can survive changing needs.

And we definitely don't want to lock up people's data! We may not have the "download all my data" feature right now, but we recognize how very important it is to the community. We'll definitely be providing a way to do it.</description>
		<content:encoded><![CDATA[<p>We don&#8217;t want to break people, and that is the heart of the problem. If we open an API, then we&#8217;d have to continue to support it no matter what. And what if that interferes with some new cool feature that we&#8217;d like to do? Eek.</p>
<p>Don&#8217;t get me wrong&#8230; I&#8217;d like to have APIs, but we&#8217;ll do it carefully so that we retain something very simple that can survive changing needs.</p>
<p>And we definitely don&#8217;t want to lock up people&#8217;s data! We may not have the &#8220;download all my data&#8221; feature right now, but we recognize how very important it is to the community. We&#8217;ll definitely be providing a way to do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PHPDeveloper.org</title>
		<link>http://benramsey.com/archives/project-hosting-on-google-code/#comment-4486</link>
		<dc:creator>PHPDeveloper.org</dc:creator>
		<pubDate>Fri, 28 Jul 2006 13:21:59 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=156#comment-4486</guid>
		<description>&lt;strong&gt;Ben Ramsey's Blog: Project Hosting on Google Code&lt;/strong&gt;

</description>
		<content:encoded><![CDATA[<p><strong>Ben Ramsey&#8217;s Blog: Project Hosting on Google Code</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Ramsey</title>
		<link>http://benramsey.com/archives/project-hosting-on-google-code/#comment-4485</link>
		<dc:creator>Ben Ramsey</dc:creator>
		<pubDate>Fri, 28 Jul 2006 10:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=156#comment-4485</guid>
		<description>The only people it will "lock in" are Google. They don't want to create an API that they will continuously break for end-users while they are still in beta. But, maybe "beta" is just an excuse for being able to break things and not have everyone get mad at you... it is "beta" after all. :-)</description>
		<content:encoded><![CDATA[<p>The only people it will &#8220;lock in&#8221; are Google. They don&#8217;t want to create an API that they will continuously break for end-users while they are still in beta. But, maybe &#8220;beta&#8221; is just an excuse for being able to break things and not have everyone get mad at you&#8230; it is &#8220;beta&#8221; after all. <img src='http://benramsey.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://benramsey.com/archives/project-hosting-on-google-code/#comment-4484</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 28 Jul 2006 08:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=156#comment-4484</guid>
		<description>So is there no way of getting your data out? How will creating an API lock anyone in?

Sounds like another typical "use opensource to create a closesource service which we then offer to opensource projects for free to generate google pageviews" move to me.</description>
		<content:encoded><![CDATA[<p>So is there no way of getting your data out? How will creating an API lock anyone in?</p>
<p>Sounds like another typical &#8220;use opensource to create a closesource service which we then offer to opensource projects for free to generate google pageviews&#8221; move to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael schurter &#187; Blog Archive &#187; Google Releases SourceForge.Net Killer</title>
		<link>http://benramsey.com/archives/project-hosting-on-google-code/#comment-4483</link>
		<dc:creator>michael schurter &#187; Blog Archive &#187; Google Releases SourceForge.Net Killer</dc:creator>
		<pubDate>Thu, 27 Jul 2006 22:56:11 +0000</pubDate>
		<guid isPermaLink="false">http://benramsey.com/?p=156#comment-4483</guid>
		<description>[...] Thanks to Ben Ramsey for live blogging a presentation on Google Code.  Google Code is SourceForge done by Google so its simpe, fast, and efficient.  (Or so they promise.) I&#8217;m moving OpenIT over to it right now as a test.  It detected that a SourceForge project of the same name already exists and allows you to e-mail the owner.  If the owner allows you to use the name, supposedly you can create the project on Google Code. [...]</description>
		<content:encoded><![CDATA[<p>[...] Thanks to Ben Ramsey for live blogging a presentation on Google Code.  Google Code is SourceForge done by Google so its simpe, fast, and efficient.  (Or so they promise.) I&#8217;m moving OpenIT over to it right now as a test.  It detected that a SourceForge project of the same name already exists and allows you to e-mail the owner.  If the owner allows you to use the name, supposedly you can create the project on Google Code. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
