WordPress foundation thinks all of the code and artwork should be GPL ? In other words our themes should be free?
Yep. Give away themes and sell support. Easy! Like wordprass.com do!Oh wait, wordpress.com users can’t do any customization, development, etc. So all that wordpress.com support is doing is kinda “to embed a gallery, click that small button…”. This means that they can hire anyone as support staff. Sure it’s easy to profit from such “support”
Envato could also launch a hosted themes service At least we won’t need to fight with $5 a year hosting issues
But I get the feeling this guy’s about something else anyways: Envato not letting the authors and copyright holders choose their licence as they see fit. I think the term he used was that being ‘evil’. And he mentioned that Envato at least allowing authors to go full GPL might be the compromise he was willing to settle the dispute. (As some may know, this happens to be the deal-breaker for me also.)
Why is Wordpress.org not letting the authors and copyright holders choose their license? I think Wordpress.org should allow to go split license.
How does allowing sleezy people to resell someone else’s work and at the same time steal their income fit the spirit of the GPL? And if it does, why do we care about the spirit of the GPL?
Well the spirit of GPL is a nice thing if you’re developing some hobby project and have income from something else, but the spirit won’t pay your bills.
I have nothing against GPL, lot of nice stuff wouldn’t be there with it. But the freedom is also to be able to choose the license and split license here is what will help to protect author’s income.
So… Let me get this straight. Because WooThemes is 100% GPL compliant, I could buy a membership for access to all their themes and then start my own website called WhewThemes and resell all their themes for half price? Can anyone give me a clear yes or not on this, because I have a plan..
Funny though is that if you purchase a theme from wordpress.com, you won’t get a source code, so you cannot reuse the theme again even though it’s GPL theme from WooCommerce. That’s how is Wordpress.com protecting their authors and making money.
I personally didn’t get the whole thing, Wordpress community is trying to enforce something that other people don’t want.
For example we wanted to release a theme on wordpress.org 100% GPL for free. We’re not allowed to do that simply because we sell themes on Themeforest and therefore we’re supporting non-gpl themes! That’s just crazy
Hi guys! Great to see everyone discussing the license updates. I’m so excited about them overall, though they are of course just one phase of a big project. We definitely know we need more individualized licenses and that’s our next port of call. There’s been a lot of discussion about the use of CC items in TF items. This is clearly an important usage, and one which we will have at the top of the list to address next.
Hi Collin, thanks for the message. When can we expect the next phase? Do you have any ETA on that? If we cannot use codecanyon items in our themes we’ll have to build them ourselves. Cheers.
I understand that since now we’re not allowed to use any items from Envato marketplaces in any stock items.
My question is, what happens to themes that already include plugins from Codecanyon?
Sorry but I didn’t find any answer to this question yet. Thanks.
I don’t think you can include plugin from Codecanyon in theme for sale anymore: http://notes.envato.com/news/marketplace-license-upgrade/
I’ve contacted Envato Support with this query today, hope I’ll get an answer soon.
I’m not quite sure if theme updates really need approvals. Updates are not being checked in details as new theme releases. We’re probably just waiting for hours for somebody just to click the button.
Theme update can be sometimes quite crucial and it’s kind of frustrating to explain to customers that they have to wait 1 day until they can download a theme where we changed one small thing.
There should be also a history of old theme versions. So in case of an unexpected bug they can always download a previous version. These things are standard in software development for years.