Quake Commitment

For those software developers and companies where open source doesn’t quite fit their business plan, how about a Quake Commitment?

“In conjunction with his self-professed affinity for sharing source code, John Carmack has open-sourced most of the major id Software engines under the GPL license. Historically, the source code for each engine has been released once the code base is 5 years old.”
Wikipedia article: id Software

Blurred Computer Commands in Green on a Black Screen

Photo "cmd.exe" cc by-sa flickr user n3wjack

I think this is a novel approach, and I’m surprised that I haven’t heard of any other companies making this sort of commitment. Fellow open source zealots would warm up to you and you’d earn the love of developer communities everywhere. It also increases the chance that your software has a greater legacy.

Let me know if you’re committing to opening the source of aged versions of your proprietary software. Will it be 2, 3 or some other length of years from now?

GPL Isn’t a Good License for Proprietary Software

Yesterday, I wrote about the clarification regarding WordPress Themes and the GPL (v2). Daniel Jalkut, who I featured as a personal WordPress Hero earlier this year, wrote one of the most interesting responses to “[WordPress] Themes are GPL, too“. Written on Thursday and temporarily taken offline by the fireball, Daniel’s “Getting Pretty Lonely” article laments that WordPress is GPL, and that any open source software that uses a GPL license discourages developer community participation.

At first this article left me very upset, maybe because I found it quite persuasive, but then I reflected that for anyone developing and selling proprietary software, Daniel’s is the only position to believe in and promote.