<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Plugin Downloads : How to use the Jivespace Plugin Directory : Comments</title>
    <link>http://www.jivesoftware.com/jivespace/docs/DOC-2280#comments</link>
    <description>Comments on : How to use the Jivespace Plugin Directory</description>
    <language>en</language>
    <pubDate>Thu, 26 Feb 2009 09:50:42 GMT</pubDate>
    <generator>Jive SBS 3.0.8 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-02-26T09:50:42Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>RE: How to use the Jivespace Plugin Directory</title>
      <link>http://www.jivesoftware.com/jivespace/docs/DOC-2280#comments-4962</link>
      <description>&lt;!-- [DocumentBodyStart:75dbe2df-7e9b-4486-8747-331b0804e57a] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;What is your process of verifying/testing plugins?&amp;#160; We're thinking about doing a similar thing with our vendors.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:75dbe2df-7e9b-4486-8747-331b0804e57a] --&gt;</description>
      <pubDate>Thu, 26 Feb 2009 09:50:42 GMT</pubDate>
      <author>ken.domen@nike.com</author>
      <guid>http://www.jivesoftware.com/jivespace/docs/DOC-2280#comments-4962</guid>
      <dc:date>2009-02-26T09:50:42Z</dc:date>
      <clearspace:dateToText>8 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
  </channel>
</rss>

