[theme-reviewers] Providing commercial non-GPL themes

[Ünsal Korkmaz]

Dont get me wrong but your saying is conflicting with this i think:
http://lists.wordpress.org/pipermail/theme-reviewers/2013-May/012868.html

I am seriously newbie on license issues and i know big problems happened in
past. I just trying to be clear as much as i can.
I will release my all commercial themes as GPL licensed. But somehow i want
to offer some non-GPL premium components to my customers like
Icomoon's Ultimate
Pack <http://icomoon.io/#icons> example. Basically everyone saying your all
content in your website must be GPL. First time i read different from only
you. This is why i am asking.



On Thu, Sep 5, 2013 at 6:01 AM, Otto <otto at ottodestruct.com> wrote:

> Look, I don't really understand why this is confusing to anybody...
>
> Are you actively selling and/or promoting non-GPL code built off of
> WordPress on your own websites? Are you then linking to those in
> themes that you're trying to get into the repository in some manner?
>
> No? Then it's probably fine. Simple. The goal is to prevent
> spammers and other marketers from getting listed by WordPress.org.
> Simple as that. You can sell your work any way you like, but the stuff
> you promote via themes in our directory must adhere to the guidelines.
> Everybody works for companies, and when you work for somebody, they
> tend to own your work. That is *normal*. The goal is to prevent spam,
> not to restrict normal behaviors or to impose ideals on other people.
>
> -Otto
>
>
>
> On Wed, Sep 4, 2013 at 9:29 PM, Ünsal Korkmaz <unsalkorkmaz at gmail.com>
> wrote:
> > So we can sell and announce non-GPL custom works in our sites without
> > breaking gpl-only rule right?
> >
> >
> > On Wed, Sep 4, 2013 at 7:11 AM, Otto <otto at ottodestruct.com> wrote:
> >>
> >> Selling custom work for clients has nothing to do with what you're
> >> affiliated with or what you're distributing or selling on your own
> >> site. That is fine.
> >>
> >> -Otto
> >>
> >>
> >> On Tue, Sep 3, 2013 at 11:05 PM, Dane Morgan <dane at danemorganmedia.com>
> >> wrote:
> >> > Chip, what about custom themes for a one off client with no intent to
> >> > distribute? I'm entertaining the idea of doing some stock themes and I
> >> > want
> >> > them to be compatible, but for the past four years I've earned my
> living
> >> > making custom themes for businesses and I built the resources they
> >> > wanted
> >> > into their themes so long as they had the legal right to use them for
> >> > that
> >> > purpose.
> >> >
> >> > Does this disqualify me out of the gate from ever getting a theme into
> >> > the
> >> > repository?
> >> >
> >> >
> >> > Chip Bennett wrote:
> >> >>
> >> >> It's really pretty simple: if you want to host *anything* at WPORG,
> you
> >> >> must be affiliated with *nothing* WordPress-related (Themes *and*
> >> >> Plugins)
> >> >> that is not GPL-compatible.
> >> >
> >> > _______________________________________________
> >> > theme-reviewers mailing list
> >> > theme-reviewers at lists.wordpress.org
> >> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >> _______________________________________________
> >> theme-reviewers mailing list
> >> theme-reviewers at lists.wordpress.org
> >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >
> >
> >
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130905/bc16de2e/attachment.html>