@hakre -

I don't really have a problem with GPL, but from the previous discussion it's seams that it's OK to distribute and use 'pirated' (or better modified themes with malicious encoded code added). What is the line on what's OK to do and what's not? It's one theme to distribute unchanged GPL theme, and completely another to add spyware and malware code to it.

I meant that WP.org as a main WordPress website on the Inernet needs to do much better job on helping users understand the implications of using pirated themes, not helping them to use it, because they will be encouriging such practices.

On so many levels WP.org is not doing a good job. It's a great for developers experienced users, but I know for sure that many users are having problem getting around that website, and that's one of the reason people running WP.org decided that is a good time to change and update and improve the website. And I hope that once that is done we will get a true WP starting point for all users. So many of the people tried to use WP.org and it's forum were more confused than anything else, starting with WP system requriements (I have written on my website about it recently) to a great deal of confusion with plugins compatibility (it's better now, but far from usable for most users). And even I as a developer, working daily with WordPress, I am avoiding WP.org as much as I can: WIKI documentation is just bad (I know it's a community thing, but WP is not just some small platform that can rely on few good will developers to write documentation, it needs a rock solid documentation that is not full of wholes and missing functions and classes), forum with too many questions unanswered (I try to answer at least 90% of questions posted about my plugins there, but most developers don't).

Point is that pirated themes are bad thing, regardless of GPL. And that's why for now WP.org needs to stick to themes in own repository. Once WP.org is changed for the better, things might be better.