<?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: Resolved:  that topics now can be</title>
	<atom:link href="http://bbpress.org/blog/2005/06/resolved-that-topics-now-can-be/feed/" rel="self" type="application/rss+xml" />
	<link>http://bbpress.org/blog/2005/06/resolved-that-topics-now-can-be/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 05 Feb 2012 20:28:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark</title>
		<link>http://bbpress.org/blog/2005/06/resolved-that-topics-now-can-be/comment-page-1/#comment-93</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 13 Jul 2005 16:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/blog/?p=13#comment-93</guid>
		<description>I agree with the first poster; why not allow this sort of information to be &quot;metadata&quot; like what was done with the user table and have a plugin interface interact with that data?

BTW, I&#039;m not a fan of mailing lists; I don&#039;t like my inbox any more cluttered than it already is. Any plans to set up an installation of bbPress on this site for development discussion?</description>
		<content:encoded><![CDATA[<p>I agree with the first poster; why not allow this sort of information to be &#8220;metadata&#8221; like what was done with the user table and have a plugin interface interact with that data?</p>
<p>BTW, I&#8217;m not a fan of mailing lists; I don&#8217;t like my inbox any more cluttered than it already is. Any plans to set up an installation of bbPress on this site for development discussion?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mdawaffe</title>
		<link>http://bbpress.org/blog/2005/06/resolved-that-topics-now-can-be/comment-page-1/#comment-85</link>
		<dc:creator>mdawaffe</dc:creator>
		<pubDate>Sun, 03 Jul 2005 00:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/blog/?p=13#comment-85</guid>
		<description>The topic resolution feature was implemented with the following fact in mind:  that bbPress is designed with the &lt;a href=&quot;http://bbpress.org/&quot; rel=&quot;nofollow&quot;&gt;explicit purpose of creating a community around support&lt;/a&gt;.

However, the software is very much still in its infancy; it&#039;s not even a year old.  Suggestions for improvements are always welcome.  Please join the &lt;a href=&quot;http://lists.bbpress.org/mailman/listinfo/bbdev&quot; rel=&quot;nofollow&quot;&gt;bbPress Development mailing list&lt;/a&gt; and discuss away.  In particular, if you&#039;ve got suggestions about extending the Plugin API, that&#039;d be great.</description>
		<content:encoded><![CDATA[<p>The topic resolution feature was implemented with the following fact in mind:  that bbPress is designed with the <a href="http://bbpress.org/" rel="nofollow">explicit purpose of creating a community around support</a>.</p>
<p>However, the software is very much still in its infancy; it&#8217;s not even a year old.  Suggestions for improvements are always welcome.  Please join the <a href="http://lists.bbpress.org/mailman/listinfo/bbdev" rel="nofollow">bbPress Development mailing list</a> and discuss away.  In particular, if you&#8217;ve got suggestions about extending the Plugin API, that&#8217;d be great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tinus Guichelaar</title>
		<link>http://bbpress.org/blog/2005/06/resolved-that-topics-now-can-be/comment-page-1/#comment-84</link>
		<dc:creator>Tinus Guichelaar</dc:creator>
		<pubDate>Fri, 01 Jul 2005 16:09:56 +0000</pubDate>
		<guid isPermaLink="false">http://bbpress.org/blog/?p=13#comment-84</guid>
		<description>Why make this a core feature? Why not focus on making plugin hooks so this can be added afterwards?</description>
		<content:encoded><![CDATA[<p>Why make this a core feature? Why not focus on making plugin hooks so this can be added afterwards?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

