[wp-hackers] One CMS to Rule Them All (was This was painful to read...)

Nathan Rice ncrice at gmail.com
Wed Dec 2 23:57:50 UTC 2009

On Wed, Dec 2, 2009 at 6:50 PM, Mike Schinkel
<mikeschinkel at newclarity.net>wrote:

> I'd be happy to write code, if I knew it would be accepted.
> I unfortunately can't afford the time to write code that will never be used
> (I wish I did have the time because I enjoy writing code, but life keeps
> getting in the way.)

That is the one risk of doing it that way. Writing code can take a while,
and it would feel like a waste of time if it wasn't accepted.

> I'd argue it's not those who produce code but those who have commit rights.
>  The latter get to decide.
True, but the people who have commit rights:
1. got those rights because they wrote patches, even some that probably
never got into core
2. feel much better about accepting patches into core if the patch actually
gets written :-)

I understand your frustration, though. You'd rather get support for a
particular feature before you waste time writing the code. Unfortunately, in
open source (and the WP community), things aren't generally done that way.
The only exception would be ideas that get debated in the weekly IRC chats.
But I've personally never seen an idea get debated on wp-hackers and
eventually make it into core. This simply hasn't been the venue in which the
WP power brokers look for ideas to include in core.

Hopefully that helps.


More information about the wp-hackers mailing list