Tag Archives: Matt Mullenweg

Will you help WordPress move away from GoDaddy?

So the drop-GoDaddy-campaign seems to have gone pretty well. Some larger sites, and many smaller sites or personal users went to another registrar. One service I noticed however that started giving me errors after distrusting GoDaddy as SSL CA was Gravatar.

Gravatar is an email-to-avatar service from Automattic – the same company that’s the main driver behind WordPress. Automattic is known for supporting free software, open web standards and the company founder Matt Mullenweg is a trustworthy supporter of both objectives. As it showed however, their domains and SSL certificates were all registered through GoDaddy. So I did a whois check and sent an e-mail to the domain administrator:

Hello, I’m curious whether Automattic has a stance on SOPA – the Stop Online Piracy Act- which is in a heated debate all over the world right now.

Why I’m asking is that I noticed (after removing GoDaddy from my trusted CA database) that the SSL certificate for wordpress.org/.com as well as domain names are registered at GoDaddy – who helped write the suggested piece of legislation. automattic.com also seems to be registered with them.

Several websites have already moved their domain names away from GoDaddy, as part of a worldwide boycott since yesterday:
http://arstechnica.com/tech-policy/news/2011/12/godaddy-faces-december-29-boycott-over-sopa-support.ars

So what can one hope for in this case? An answer with “why yes of course, we will spend several work hours changing registrar and certificate authority just to make you happy”? Or a more modest “it is in our interest that blah blah, but you know they did change their mind about SOPA” or something along those lines? Well, the response was one of the more modest ones:

Hi,

Thanks for your suggestion. We’ve registered your suggestion and will keep it in mind.

Sorry for the inconvenience.

Best,
Karim – Happiness Engineer
Automattic | WordPress.com

“Sorry for the inconvenience”? I sincerely enjoyed that expression! In any case, I was hoping that this post might generate some interest with my readers to send off an e-mail to support@wordpress.com or domains@automattic.com requesting they leave GoDaddy’s services. Wikipedia and many others have already done it or are in the process of doing it.

WordPress requires themes to be GPL

Andrew Warner at Mixergy has published a discussion [MP3, transcript] between Chris Pearson (founder of Thesis, a very advanced WordPress theme) and Matt Mullenweg (who I’d call Mr. WordPress). This is a perfect example of what the debate between the copyright industry vs. iPirates (intellectual property pirates) is like. A very interesting software license and copyright debate, if you ask me.

Matt responds well to a long rant (blah blah, can’t make money if it’s freely licensed) by Chris. Start listening at 16:30 if you wish to hear the end of the rant and the response. The bottom line is that Chris Pearson sees Thesis – which requires WordPress – as entirely his own property which no one can use. He’s just out to state that “he’s not a follower” and says that Matt is trying “to dictate” usage through the GPL.

Chris Pearson refers at 8:30 to “Mike Wasylik” (he says Brian), an attorney who has written “Why the GPL doesn’t apply to premium WordPress themes“. However not related to the same kind of dilemma WordPress vs. Thesis is about. Mike Wasylik’s examples are related to the Game Genie’s modification of running binaries of Nintendo games – which does not apply at all to the source code license which the GPL is.

Also, Chris mentions that WordPress “is only a backend” and that “WordPress [on its own] only serves a blank page”. What he forgets is that WordPress also serves an API over XML-RPC etc….

But, to the point of license debating. Mark Jaquith posts the most convincing argument in this debate:

It isn’t correct to think of WordPress and a theme as separate entities. As far as the code is concerned, they form one functional unit. The theme code doesn’t sit “on top of” WordPress. It is within it, in multiple different places, with multiple interdependencies.

Basically: Thesis (or any WP theme), when used, becomes a part of that running copy of WordPress. At source code and PHP interpretation level. Thus, at that specific point, the GPL must be followed. To clear things up, Mark Jaquith also mentions the API system:

WordPress has many external APIs that spit out data. Interacting with these APIs does not put your code on the same level as core WordPress code.

(Oh, and Thesis have actually copied large pieces of code from WordPress.)

Update: Thesis now has a split license PHP code is GPLv2, everything else (CSS, images, added JS etc.) . Probably because of the bad press. Unfortunately this means that Chris Pearson probably didn’t learn anything in the process except perhaps humility. It’d be cool though if the license for CSS and images were Free too. At least it’d mend the community’s wounds a bit.