1. Ryan

    The issues you have outlined above seem to be the same reasons I hear from Habari developers about why they jumped ship.

    I’m fairly happy with the way things work though. WordPress is the best product out there so whatever they’re doing seems to be working. If it aint broke, don’t fix it!


  2. Trace

    I don’t have enough experience to directly contribute to the code base, so I can’t really answer the question in regards to WP, but I will say that in my experience with non-code related group tasks, there is probably nothing worse than the decision making or lack thereof that occurs in heavily democratic committee like decision making structures.

    The bottom line is that everyone has an opinion, but that doesn’t mean they are all equal in terms of quality. This is even true of customer opinions. As much as you want to value that feedback and each voice, some opinions are simply just noise and your business will be hurt by acting on them. In fact, I know many entrepreneurs who swear that their pricing model is not tweaked enough (read high enough) until they get a certain percentage of complaints / gripes from users. So the feedback can be useful, but not necessarily for the reason one would think.

    What’s the old saying? A camel is a horse built by committee? Something like that.

    The point is that is that if WP is not as responsive or open to direct community feedback (no clue if this is true), it doesn’t necessarily mean it’s a bad thing (although I can see how it would frustrate folks) and in fact may be one of the distinguishing characteristics that have helped WP progress as successfully as it has….


  3. Chip Bennett

    There are advantages and disadvantages to either approach.

    Of course, the Ubuntu model works, and it works very well. Ubuntu is very clearly a community project, yet also has a very clear decision-making structure in place, headed by “SABDFL” (Self-Appointed Benevolent Dictator For Life) Mark Shuttleworth.

    Of course, Mark Shuttleworth is an amazing leader and businessman, and uses his SABDFL position very wisely. (Shuttleworth earned his hundreds of millions the hard way, building a business on his own, before allowing himself to be bought out and then using his money to launch/support Ubuntu.)

    Not to say that it can’t get there, but WordPress just isn’t there yet.

    Perhaps Matt Mullenweg will prove to be the same sort of canny businessman and leader. Matt is an incredibly charismatic, enthusiastic, and intelligent leader for WordPress, but IMO still has the business acumen and maturity of the 25 year old that he is. (And there’s nothing inherently wrong with that; after all, look at what Bill Gates built, from much the same start.)

    With all that said, if Matt wants to keep WordPress as his (and Automattic’s) baby, that’s fine. The model has obviously worked fabulously thus far.

    My main frustration on this issue is when WordPress tries to take advantage of the benefits of being ostensibly a “community” project, while at the same time not relinquishing the control/decision-making to that same community. Choose a position, and then live with the advantages and disadvantages of that decision; don’t try to straddle the fence.

    Personally, I’d be fine with whichever way the decision were made. I love WordPress and don’t ever see myself using anything else.


  4. Kevin Paquet

    WordPress is a theme and plugin author run project that slowly turns to a commercial mess with all the plugin and theme authors going commercial GPL.

    Wake up, you started in the first place to contribute to the community with what you have been doing. And goign GPL erases the FREE in WordPress since WordPress would be nothing without the great plugins (that sooner or later you’re having to pay for)


  5. Ryan

    I found a link this evening which does a good job of explaining reasons why WordPress should not become a fully community run project:


  6. Aaron D. Campbell

    I think you said it perfectly when you said that “it’s development is largely community driven.” It’s not community “run” but it is community “driven”. If the project were community run, you’d quickly face the “too many chiefs not enough Indians” dilemma, which causes the project to grind to a halt. If 1,000 people think they all have equal say on a matter, you unfortunately don’t end up with 600 wanting option A and 400 wanting option B. Instead you end up with options A, B, C, D, E, F, G, H, I, and J each with roughly 100 supporters. How do you handle that? Which option do you go with? The unfortunate answer is that usually none of them get done, even if 9 of the 10 options are horrible.


  7. Jeffro

    Well, I have changed my mind in that Matt Mullenweg is really not the sole decision maker for the WordPress.org software anymore. As I’ve discussed with a few people and have witnessed what goes on in the Developer chats, the decision process is spread amongst a few people, namely the core commiters who then delegate feature development to whomever wants to take a stab at it. Those who participate in the dev chat get a say with the topics discussed in the chat and you can vote yes or no or provide alternatives or whatever.

    Also based on my discussions, Matt appears to be more involved from a development standpoint with WordPress.com and not so much with WordPress.org. He is more of a delegator than anything else.

    So with all that in mind and what I’ve experienced, I say the WordPress project is definitely community driven with plenty of opportunities to voice an opinion and contribute to the project without one persons purpose getting in the way.


Comments are closed.

%d bloggers like this: