Category Archives: Open Source

Free and open source software, licensing, community, and why it matters.

“The reality is that more and more decisions, including decisions about life and death, are being made by software,” Thomas Dullien, a well-known security researcher and reverse engineer who goes by the Twitter handle Halvar Flake, said in an email. “But for the vast majority of software you interact with, you are not allowed to examine how it functions,” he said.

The Times has a great look at hacker and car manufacturer mishaps and makes the case over and over again for Open Source. It’s great to see more of the world waking up to the importance of open source.

There is No Such Thing as a Split License

Ideas, Open Source, Themes

There’s a term that pops in the WordPress community, “split license”, that we should put to rest. It’s sloppy at best, misleading at worst.

First, some background. WordPress is under a license called the GPL, which basically says you can do whatever you like with the software, but if you distribute changes or create derivative works they also need to be under the GPL. Think of it like a Creative Commons Sharealike license.

In the past people weren’t sure if themes for WordPress were derivative works and needed to be GPL. In 2009 we got an outside legal opinion that cleared up the matter saying that the PHP in themes definitely had to be GPL, and for CSS and images it was optional. Basically everyone in the WP community went fully GPL, sometimes called 100% GPL, for all the files required to run their theme (PHP, JS, CSS, artwork). The predicted theme apocalypse and death of WordPress didn’t happen and in fact both theme shops and WordPress flourished, and best of all users had all the same freedoms from their themes as they got from WordPress. It was controversial at the time, but I think history has reflected well on the approach the WP community took.

As I said the PHP has to be GPL, the other stuff can be something else — many people started to use the term “split license” or “split GPL” to describe this. The problem, especially with the latter, is it leaves out the most important information. “Split GPL” doesn’t say whether the theme is violating WordPress’ license or not (maybe it’s proprietary PHP and GPL CSS), and more importantly doesn’t say what the non-GPL stuff is, which is the part you need to worry about! It also makes it sound like a split license is a thing, when all it really means is there are different licenses for different parts of the work. If something has a “split license” you have no idea what restrictions or freedoms it provides.

If someone decides to have different licenses for different parts of a theme they ship in one package, it’s probably worth taking a few extra words to spell out what the rights and restrictions are, like “GPL PHP, and a restrictive proprietary license for all other elements included with the theme.” This is really important because if you’re a smart WordPress consumer you should avoid proprietary software, there is always a GPL alternative that gives you the rights and freedoms you deserve, and probably is from a nicer person who is more in line with the philosophy of the rest of WordPress. Vote with your pocketbook, buy GPL software!

 

How Facebook is eating the $140 billion hardware market — I’ve always said that open source eventually dominates every market it enters, and with enterprise hardware it’s in the very, very early stages but this article is chock-full of examples of the economies of scale when companies start collaborating on shared problems. The problem is one company’s inefficiency and wasted cost is another company’s revenue. Cool to look at in the context of yesterday’s post on government.

“Apple Lossless, also known as ALAC, is a lossless audio codec Apple developed some time ago for digital music. The codec compresses music files anywhere from 40-60 percent of their original size with no discernible loss in audio quality or fidelity.” — Apples ALAC codec is now open source. About a year and a half ago I started re-ripping all my music in ALAC, it’s fantastic, especially now that iTunes can down-convert when syncing to iPhones / iPods.

A New Home for the WordPress Trademark

Automattic, Essays, Open Source, Personal, WordPress,

As I write this, I’m on my way to Seaside, Florida to see 60+ Automatticians at our yearly meetup. More than sixty… that number astounds me! Automattic has grown so far beyond what I originally imagined and every day I’m amazed by my colleagues and the things they create. Today we’re growing in another way: Automattic has transferred the WordPress trademark to the WordPress Foundation, the non-profit dedicated to promoting and ensuring access to WordPress and related open source projects in perpetuity. This means that the most central piece of WordPress’s identity, its name, is now fully independent from any company.

This is a really big deal.

I want to recognize and applaud the courage and foresight of Automattic’s board, investors, and legal counsel who made this possible: Mike Hirshland, Phil Black, Tony Conrad, Toni Schneider, Gunderson Dettmer. I’d also like to thank Matt Bartus of Dorsey & Whitney for their counsel on the Foundation side. The WordPress brand has grown immeasurably in the past 5 years and it’s not often you see a for-profit company donate one of their most valuable core assets and give up control. However, I know in my heart that this is the right thing for the entire WordPress community, and they followed me on that. It wasn’t easy, but things worth doing seldom are.

When Automattic registered the WordPress trademark back in 2006, we were a small startup of a few people: a business founded largely to enable us to work on WordPress full-time instead of hacking around our day jobs. A lot has changed since then — somehow along the way we ended up with an audience of a quarter billion people — but a lot has stayed the same. We’re still a group of people in love with WordPress and free/open source software and we’re lucky to have figured out a way to contribute to the world and flourish as a business while doing it.

Automattic might not always be under my influence, so from the beginning I envisioned a structure where for-profit, non-profit, and not-just-for-profit could coexist and balance each other out. It’s important for me to know that WordPress will be protected and that the brand will continue to be a beacon of open source freedom regardless of whether any company is as benevolent as Automattic has been thus far. It’s important to me to know that we’ve done the right thing. Hopefully, it’s important to you, too, and you’ll continue your support of WordPress, the WordPress Foundation, and Automattic’s products and services. We couldn’t do it without you!

Facebook McAfee

Facebook, Food, Open Source, Personal

Facebook is offering its users a 6-month free trial of McAfee and promoting it heavily, and even forcing people to run a scan before they can reactivate a hacked account. They’re “not aware of another free Internet service that takes this much responsibility for helping people keep their accounts secure.” (Didn’t Google promote McAfee through Google Pack at one point?) I think this is a laudable step, more security is intrinsically good, but I have to suspect this is more about revenue than security. They will probably make many millions of dollars from their users installing or buying McAfee as a result of this.

Modern versions of Windows include free tools like Defender which are just as good and appear to have less of a performance impact on the computer. But if they really wanted to have a long-term impact on desktop as a vector for attack on web services I’m surprised they didn’t start, sponsor, or promote an Open Source equivalent of McAfee. This seems like a space very well-suited to address with an OS tool in the digital commons, much like a Windows anti-spyware equivalent of SpamAssassin, with self-updating rules and a completely transparent process.

New WP.org Search

Open Source, Search, WordPress

At the last IRC meetup the WordPress community asked for better search that included both the forums and the Codex and was integrated with the look and feel of the rest of the site. When I did this before it was horribly slow and it involved several queries across several different programs and MySQL hosts to get the results from the wiki, the forums, the blog, and then splice them together somehow. Later we switched to a plain Google site-search but they didn’t like the HTML we used for the search form so we took it down. Well after the meeting I remembered Yahoo Developer Network which had some sort of API for their search with a much higher limit than Google’s.

I went to the site to see how much of a pain it would be so I could start properly procrastinating, but I was taken aback by how incredibly easy it was to get an application ID and start getting the results back as simple XML. I began hacking on it right then. It was about 5 minutes to set up a search form with URIs the way I wanted, 7 minutes to get the XML and parse it out, 5 minutes to write in some paging, and then about 20 minutes tweaking the search page to make it look a little better. The result is the new search.wordpress.org WordPress Search.

It still needs some more work. There seems to be a dupe problem, which is actually a problem with our site, not Yahoo Search. I’d like to tweak the results to highlight newer topics more, or at leats allow for a date-based weighting. Finally I think it would be nice to include some WP-related blogs like Blogging Pro and Weblog Tools Collection in the results. Most importantly we now have a clean URI structure and home for searches which is abstracted from any piece of software or particular service provider. Yahoo deserves major kudos for opening up their information in such a free way and making it so easy that it’s taken me longer to write this post than start using their API.