

<?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: WordPress Plugin Development, What Not to Do</title>
	<atom:link href="http://wpvibe.com/plugin-development-what-not-to-do-243/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpvibe.com/plugin-development-what-not-to-do-243/</link>
	<description>Just another EMV Network Site site</description>
	<lastBuildDate>Fri, 14 Oct 2011 03:38:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Jonathan Dingman</title>
		<link>http://wpvibe.com/plugin-development-what-not-to-do-243/#comment-282</link>
		<dc:creator>Jonathan Dingman</dc:creator>
		<pubDate>Sat, 13 Feb 2010 18:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://wpvibe.com/?p=243#comment-282</guid>
		<description>Matt is more the co-founder/founder of WordPress, not Automattic.  Matt isn&#039;t even the CEO of &quot;WordPress,&quot; &lt;a href=&quot;http://wpvibe.com/interview-automattic-wordpress-ceo-toni-schneider-196/&quot; rel=&quot;nofollow&quot;&gt;Toni Schneider is&lt;/a&gt;.  But Matt is still the forward facing person of WordPress, so it could be easy to get that mixed up.

As far as Akismet becoming part of the core, I can definitely understand your concerns with it.  I personally love Akismet, so I&#039;m not to have too much pushback from wanting it to be part of the core, but I can understand other people not wanting it to be part of the core simply because they may not want to use it.</description>
		<content:encoded><![CDATA[<p>Matt is more the co-founder/founder of WordPress, not Automattic.  Matt isn&#8217;t even the CEO of &#8220;WordPress,&#8221; <a href="http://wpvibe.com/interview-automattic-wordpress-ceo-toni-schneider-196/" rel="nofollow">Toni Schneider is</a>.  But Matt is still the forward facing person of WordPress, so it could be easy to get that mixed up.</p>
<p>As far as Akismet becoming part of the core, I can definitely understand your concerns with it.  I personally love Akismet, so I&#8217;m not to have too much pushback from wanting it to be part of the core, but I can understand other people not wanting it to be part of the core simply because they may not want to use it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leif Andersen</title>
		<link>http://wpvibe.com/plugin-development-what-not-to-do-243/#comment-281</link>
		<dc:creator>Leif Andersen</dc:creator>
		<pubDate>Sat, 13 Feb 2010 18:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://wpvibe.com/?p=243#comment-281</guid>
		<description>Thanks, you to.

Although, based on this video from Matt&#039;s blog: http://ma.tt/2009/11/this-week-in-startups/ I thought that he was the founder of automattic, but I guess I could have been wrong about that.

Hmmm...I don&#039;t know how I feel about akismet becoming a core part of wordpress.  It&#039;s fine as an add on, that way people who don&#039;t like having to use locked down plugins can just remove it (I like akismet, but I could see others not liking it), however, putting akismet into the core would mean that it would be much more work to remove it if you felt obligated to do so.</description>
		<content:encoded><![CDATA[<p>Thanks, you to.</p>
<p>Although, based on this video from Matt&#8217;s blog: <a href="http://ma.tt/2009/11/this-week-in-startups/" rel="nofollow">http://ma.tt/2009/11/this-week-in-startups/</a> I thought that he was the founder of automattic, but I guess I could have been wrong about that.</p>
<p>Hmmm&#8230;I don&#8217;t know how I feel about akismet becoming a core part of wordpress.  It&#8217;s fine as an add on, that way people who don&#8217;t like having to use locked down plugins can just remove it (I like akismet, but I could see others not liking it), however, putting akismet into the core would mean that it would be much more work to remove it if you felt obligated to do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dre Armeda</title>
		<link>http://wpvibe.com/plugin-development-what-not-to-do-243/#comment-280</link>
		<dc:creator>Dre Armeda</dc:creator>
		<pubDate>Fri, 12 Feb 2010 04:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://wpvibe.com/?p=243#comment-280</guid>
		<description>Most definitely Leif, agreed. 

Couple things on that:

From my understanding Mark is not an Automattic employee. 

Secondly, I am under the impression that Akismet will become a core plugin and will no longer part of the default WordPress installation.

Thanks for your comments, have a great weekend.

~da</description>
		<content:encoded><![CDATA[<p>Most definitely Leif, agreed. </p>
<p>Couple things on that:</p>
<p>From my understanding Mark is not an Automattic employee. </p>
<p>Secondly, I am under the impression that Akismet will become a core plugin and will no longer part of the default WordPress installation.</p>
<p>Thanks for your comments, have a great weekend.</p>
<p>~da</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leif Andersen</title>
		<link>http://wpvibe.com/plugin-development-what-not-to-do-243/#comment-279</link>
		<dc:creator>Leif Andersen</dc:creator>
		<pubDate>Fri, 12 Feb 2010 04:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://wpvibe.com/?p=243#comment-279</guid>
		<description>I agree with this list.  However, I must laugh at two of them:

&quot;Harvest people’s e-mail addresses or require registration to activate the plugin.

Explicitly state or imply that users of the plugin must pay you money in order to use the plugin.&quot;

Akismet breaks both of those rules, and not only is it made by automattic, but it&#039;s even built into wordpress.</description>
		<content:encoded><![CDATA[<p>I agree with this list.  However, I must laugh at two of them:</p>
<p>&#8220;Harvest people’s e-mail addresses or require registration to activate the plugin.</p>
<p>Explicitly state or imply that users of the plugin must pay you money in order to use the plugin.&#8221;</p>
<p>Akismet breaks both of those rules, and not only is it made by automattic, but it&#8217;s even built into wordpress.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

