<?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: Announcing the Launchpad bug plugin API spec</title>
	<atom:link href="http://blog.launchpad.net/cool-new-stuff/announcing-the-launchpad-plugin-api-spec/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.launchpad.net/cool-new-stuff/announcing-the-launchpad-plugin-api-spec</link>
	<description>Thoughts from the Launchpad team</description>
	<lastBuildDate>Mon, 16 Nov 2009 11:43:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Launchpad News</title>
		<link>http://blog.launchpad.net/cool-new-stuff/announcing-the-launchpad-plugin-api-spec/comment-page-1#comment-20111</link>
		<dc:creator>Launchpad News</dc:creator>
		<pubDate>Thu, 18 Dec 2008 18:04:15 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/?p=306#comment-20111</guid>
		<description>[...] Graham has more in his blog post. [...]</description>
		<content:encoded><![CDATA[<p>[...] Graham has more in his blog post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Reese</title>
		<link>http://blog.launchpad.net/cool-new-stuff/announcing-the-launchpad-plugin-api-spec/comment-page-1#comment-18874</link>
		<dc:creator>John Reese</dc:creator>
		<pubDate>Fri, 05 Dec 2008 13:44:26 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/?p=306#comment-18874</guid>
		<description>Hi!  I&#039;ve just created a report submitted to the MantisBT tracker covering this topic, #9940 [1].  However, I would like to point out that the proper URL to the MantisBT project is http://mantisbt.org - no hyphen.  Thank you, and we look forward to allowing upstream projects using our software to integrate with Launchpad!

[1] http://www.mantisbt.org/bugs/view.php?id=9940

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi!  I&#8217;ve just created a report submitted to the MantisBT tracker covering this topic, #9940 [1].  However, I would like to point out that the proper URL to the MantisBT project is <a href="http://mantisbt.org" rel="nofollow">http://mantisbt.org</a> &#8211; no hyphen.  Thank you, and we look forward to allowing upstream projects using our software to integrate with Launchpad!</p>
<p>[1] <a href="http://www.mantisbt.org/bugs/view.php?id=9940" rel="nofollow">http://www.mantisbt.org/bugs/view.php?id=9940</a></p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jef Spaleta</title>
		<link>http://blog.launchpad.net/cool-new-stuff/announcing-the-launchpad-plugin-api-spec/comment-page-1#comment-18844</link>
		<dc:creator>Jef Spaleta</dc:creator>
		<pubDate>Thu, 04 Dec 2008 19:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/?p=306#comment-18844</guid>
		<description>This is a good step. I applaud it.  In fact in some ways release an extensive API aimed at cross-project collaboration is better than just opening launchpad&#039;s source.  

The reality is, we live in an age where multiple implementations for project services are going to exist. No one codebase, no one service, is going to encompass all open ecosystem development. We as a distributed set of projects and communities need to figure out how to have our tools talk across those project and community boundaries.   Having a set of APIs that cover as many aspects as possible are the way to go.  

So now that you&#039;ve started releasing a set of APIs that are launchpad specific.  I challenge you to take the next step and coordinate a discussion with other tool developers about how to craft a set of APIs that all collaborative tools can code for so information can be shared across projects as easily as possible.   


-jef</description>
		<content:encoded><![CDATA[<p>This is a good step. I applaud it.  In fact in some ways release an extensive API aimed at cross-project collaboration is better than just opening launchpad&#8217;s source.  </p>
<p>The reality is, we live in an age where multiple implementations for project services are going to exist. No one codebase, no one service, is going to encompass all open ecosystem development. We as a distributed set of projects and communities need to figure out how to have our tools talk across those project and community boundaries.   Having a set of APIs that cover as many aspects as possible are the way to go.  </p>
<p>So now that you&#8217;ve started releasing a set of APIs that are launchpad specific.  I challenge you to take the next step and coordinate a discussion with other tool developers about how to craft a set of APIs that all collaborative tools can code for so information can be shared across projects as easily as possible.   </p>
<p>-jef</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: P</title>
		<link>http://blog.launchpad.net/cool-new-stuff/announcing-the-launchpad-plugin-api-spec/comment-page-1#comment-18841</link>
		<dc:creator>P</dc:creator>
		<pubDate>Thu, 04 Dec 2008 16:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://news.launchpad.net/?p=306#comment-18841</guid>
		<description>Amusing. :-)

Launchpad has its own bug tracker and still has to explicitly say &quot;We in the Launchpad team realise, of course, that Bugzilla and Trac aren’t the only two bug trackers in the world.&quot;

:-)</description>
		<content:encoded><![CDATA[<p>Amusing. <img src='http://blog.launchpad.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Launchpad has its own bug tracker and still has to explicitly say &#8220;We in the Launchpad team realise, of course, that Bugzilla and Trac aren’t the only two bug trackers in the world.&#8221;</p>
<p> <img src='http://blog.launchpad.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
