<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Brilliant but Cranky Plugin Developer Forks WordPress</title>
	<link>http://www.adammessinger.com/2005/04/19/wordpress-forked</link>
	<description></description>
	<pubDate>Tue, 16 Mar 2010 00:15:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Adam Messinger</title>
		<link>http://www.adammessinger.com/2005/04/19/wordpress-forked#comment-4731</link>
		<pubDate>Tue, 19 Apr 2005 19:42:25 +0000</pubDate>
		<guid>http://www.adammessinger.com/2005/04/19/wordpress-forked#comment-4731</guid>
					<description>Thanks for the additional clarification. I've updated the post to refer to your comment.</description>
		<content:encoded><![CDATA[<p>Thanks for the additional clarification. I&#8217;ve updated the post to refer to your comment.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dr Dave</title>
		<link>http://www.adammessinger.com/2005/04/19/wordpress-forked#comment-4729</link>
		<pubDate>Tue, 19 Apr 2005 19:19:11 +0000</pubDate>
		<guid>http://www.adammessinger.com/2005/04/19/wordpress-forked#comment-4729</guid>
					<description>In fact, if you will allow me to specify even more (yea, I know: given the numbers of times I've had to go back and explicit the meaning of my original intent, it should be pretty clear by now that I am not cut to do news press releases):

That snapshot of the code is, indeed, not a fork.

Nor is it a proprietary patch.

Nor does it contain the slightest modification specifically targeted at running Spam Karma...

It's a honest to goodness snapshot of the WP development effort, at a specific time (04/16/05, to be precise). With not a single change, except for an altered ReadMe that stripped the invitation to submit issues in the wp.org forums.

As it happens, it contains (among others) a bug-fix, made by WP developers, and addressing a 1.5 problem that prevents lots of plugins from working correctly with that release (SK, you guessed it, being one of them).

In fact, some new elements have come to my knowledge today that only reinforce my conviction this was my best option. I won't elaborate on them, because I would most definitely sound snide once again, but invite you to read: http://trac.wordpress.org/changeset/2536 and judge for yourself...

Thanks a lot for bringing your arbitration to the debate and allowing me to respond here...</description>
		<content:encoded><![CDATA[<p>In fact, if you will allow me to specify even more (yea, I know: given the numbers of times I&#8217;ve had to go back and explicit the meaning of my original intent, it should be pretty clear by now that I am not cut to do news press releases):</p>
<p>That snapshot of the code is, indeed, not a fork.</p>
<p>Nor is it a proprietary patch.</p>
<p>Nor does it contain the slightest modification specifically targeted at running Spam Karma&#8230;</p>
<p>It&#8217;s a honest to goodness snapshot of the WP development effort, at a specific time (04/16/05, to be precise). With not a single change, except for an altered ReadMe that stripped the invitation to submit issues in the wp.org forums.</p>
<p>As it happens, it contains (among others) a bug-fix, made by WP developers, and addressing a 1.5 problem that prevents lots of plugins from working correctly with that release (SK, you guessed it, being one of them).</p>
<p>In fact, some new elements have come to my knowledge today that only reinforce my conviction this was my best option. I won&#8217;t elaborate on them, because I would most definitely sound snide once again, but invite you to read: <a href='http://trac.wordpress.org/changeset/2536' rel='nofollow'>http://trac.wordpress.org/changeset/2536</a> and judge for yourself&#8230;</p>
<p>Thanks a lot for bringing your arbitration to the debate and allowing me to respond here&#8230;
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
