Hacker News thread discussing GPL for WordPress themes. Yes it’s that GPL talk again, but discussions on Hacker News are always worth reading.
I thought licensing your theme with GPL is enough to get it included on the Theme Directory, but looks like I’m wrong. Matthew Lyle’s Elegant Blog theme is rejected because his site advertises Thesis and Themeforest:
You must either create a separate website to house them, or remove any “support” of non-GPL themes from your website. This would include advertisements for something like the Thesis theme, ThemeForest, and also any paid themes that you’ve created in the past that are not GPL compatible.
I didn’t follow WordPress’ history from the beginning, so not quite sure what to make of this post. Read through all the comments too, guys. Matt and Mark Jaquith weighed in there too, among others.
Matt Mullenweg wrote the Not Lonely At All essay to reply Daniel Jalkut’s previous article about the possibility for WordPress to have a stronger community if it embraced the less restrictive BSD-style license. There are long discussions on both posts, and I think Gina Trapani’s opinion on this is worth the read, too.
Also, here’s John Gruber’s response to Matt’s post.
Finally, a definitive source on the long talked about issue:
One sentence summary: PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.
This matches with what I (and many others) believed so far. Also note that the post says that WordPress.org will only promote 100% GPL or compatible themes, which I assume means that you have to GPL your CSS and images too for your theme to be accepted there.