<?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: On WordPress.com theme Marketplace</title>
	<atom:link href="http://www.patriciamuller.com/wordpress/wpcom-marketplace/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.patriciamuller.com/wordpress/wpcom-marketplace/</link>
	<description>Writes about internet, technology and geek life.</description>
	<pubDate>Sat, 31 Jul 2010 16:24:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: KWiz</title>
		<link>http://www.patriciamuller.com/wordpress/wpcom-marketplace/#comment-254</link>
		<dc:creator>KWiz</dc:creator>
		<pubDate>Sat, 05 Jan 2008 18:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.patriciamuller.com/wordpress/wpcom-marketplace/#comment-254</guid>
		<description>Hi Patricia,
I'm not a developer; I'm an "end-user"; you know, one of those who doesn't have much of a clue about CCS and HTML.  So I see incredible value in making available "premium" themes for people to purchase.  In fact, I did purchase one, and am working on it right now.  The price was under $60, and it is highly customizable.  It has a great deal of features, I know I won't be able to take advantage of all of them.  Yet, the great thing about the theme I purchased is that the developer of the theme offers FANTASTIC support!  As soon as I looked at the theme once I purchased it, I said, Whoa!  But as soon as I began sending emails to the developer asking questions about how to do things, I got fantastic response and support.  Mind you, I am attempting to discover how to do these things on my own, but when I get stuck, the developer responds by email promptly (within a day or less, usually).  

So I'm all for paid premium themes.  But in my mind, the developer (or someone) must be willing to provide good support for those who pay for their premium themes (and I'm assuming those are people like me who have very limited - but improving - skills in CSS and HTML).</description>
		<content:encoded><![CDATA[<p>Hi Patricia,<br />
I&#8217;m not a developer; I&#8217;m an &#8220;end-user&#8221;; you know, one of those who doesn&#8217;t have much of a clue about CCS and HTML.  So I see incredible value in making available &#8220;premium&#8221; themes for people to purchase.  In fact, I did purchase one, and am working on it right now.  The price was under $60, and it is highly customizable.  It has a great deal of features, I know I won&#8217;t be able to take advantage of all of them.  Yet, the great thing about the theme I purchased is that the developer of the theme offers FANTASTIC support!  As soon as I looked at the theme once I purchased it, I said, Whoa!  But as soon as I began sending emails to the developer asking questions about how to do things, I got fantastic response and support.  Mind you, I am attempting to discover how to do these things on my own, but when I get stuck, the developer responds by email promptly (within a day or less, usually).  </p>
<p>So I&#8217;m all for paid premium themes.  But in my mind, the developer (or someone) must be willing to provide good support for those who pay for their premium themes (and I&#8217;m assuming those are people like me who have very limited - but improving - skills in CSS and HTML).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mauro</title>
		<link>http://www.patriciamuller.com/wordpress/wpcom-marketplace/#comment-180</link>
		<dc:creator>Mauro</dc:creator>
		<pubDate>Mon, 12 Nov 2007 23:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.patriciamuller.com/wordpress/wpcom-marketplace/#comment-180</guid>
		<description>Oi Patricia :)

Lancei um Tag para você participar num Meme.
38 Things About You :)

Espero que esteja melhorando rápido da cirurgia :)</description>
		<content:encoded><![CDATA[<p>Oi Patricia <img src='http://www.patriciamuller.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Lancei um Tag para você participar num Meme.<br />
38 Things About You <img src='http://www.patriciamuller.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Espero que esteja melhorando rápido da cirurgia <img src='http://www.patriciamuller.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adam</title>
		<link>http://www.patriciamuller.com/wordpress/wpcom-marketplace/#comment-178</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Sun, 11 Nov 2007 15:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.patriciamuller.com/wordpress/wpcom-marketplace/#comment-178</guid>
		<description>Great thoughts.  I think the biggest sticking point for me is still the exclusivity section.  I don't really know where to go with that.  I think that it's a bit much to ask designers to hand over every right to the theme (under the GPL) with little guarantee in return.  

Support is another big issue, not so much for the designer as for the users.  The amount of support of course depends on the quality of the original theme, to a degree.  I would hope that automattic would attempt to handle most of the support internally, since they'll be the ones with access to the theme.</description>
		<content:encoded><![CDATA[<p>Great thoughts.  I think the biggest sticking point for me is still the exclusivity section.  I don&#8217;t really know where to go with that.  I think that it&#8217;s a bit much to ask designers to hand over every right to the theme (under the GPL) with little guarantee in return.  </p>
<p>Support is another big issue, not so much for the designer as for the users.  The amount of support of course depends on the quality of the original theme, to a degree.  I would hope that automattic would attempt to handle most of the support internally, since they&#8217;ll be the ones with access to the theme.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
