[theme-reviewers] GPL-Compatibility

Thu Jun 5 12:51:38 UTC 2014

I understand the screenshots are already policed and GPL applies to
whole.theme. This is very clear. The question are:

- if we require theme authors to explicitly declare the source and licence
for every single image (including images used in screenshot).
- if the reviewer has to verify every single source.

If this is the case, many (if not most) themes fail this criteria.

On Thu, Jun 5, 2014 at 8:45 AM, Chip Bennett <chip at chipbennett.net> wrote:

> The Guidelines already state "100% GPL" for *everything* bundled with the
> Theme. I'm not sure how much clearer or more explicit they can be?
>
>
> On Thu, Jun 5, 2014 at 8:33 AM, rose tail <metallicarosetail at gmail.com>
> wrote:
>
>> Yes exactly setting the new guideline is the best way for reviewer
>>
>>
>> On Thu, Jun 5, 2014 at 6:16 PM, Stephen Cui <scui2005 at gmail.com> wrote:
>>
>>> Are we going to police the screenshot? I feel that we may went too far
>>> for reviewer. If this is the case, we will have to set the guideline for
>>> reviewers.
>>>
>>>
>>> On Thu, Jun 5, 2014 at 8:11 AM, Srikanth Koneru <tskk79 at gmail.com>
>>> wrote:
>>>
>>>> so many themes were approved with unsplash and pixabay images, have to
>>>> watch the #1 queue carefully
>>>>
>>>>
>>>> On Thu, Jun 5, 2014 at 5:32 PM, Chip Bennett <chip at chipbennett.net>
>>>> wrote:
>>>>
>>>>> Pixabay appears to be a site where copyright holders upload their
>>>>> images, and upon upload, Pixabay says, "by uploading, you agree to
>>>>> distribute your pictures under the terms we specify".
>>>>>
>>>>> So, if the images are Public Domain outside of/prior to uploading to
>>>>> Pixabay, then they remain Public Domain. But if the images are only CC0
>>>>> because of the act of uploading to Pixabay, then they would be under the
>>>>> *actual* terms of the site. And those *actual* terms impose
>>>>> non-GPL-compatible restrictions.
>>>>>
>>>>> So again: you have to go back to the license specified by the
>>>>> copyright holder.
>>>>>
>>>>>
>>>>> On Thu, Jun 5, 2014 at 7:53 AM, Srikanth Koneru <tskk79 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> But sometime back, you said the CC0 mentioned on the image overrides
>>>>>> that and you okayed pixabay, so that is now null and void?
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 5, 2014 at 5:21 PM, rose tail <
>>>>>> metallicarosetail at gmail.com> wrote:
>>>>>>
>>>>>>> Thanks a lot for you suggestion
>>>>>>> :)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 5, 2014 at 5:33 PM, Chip Bennett <chip at chipbennett.net>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Looking at the site's license terms:
>>>>>>>> http://pixabay.com/en/service/terms/
>>>>>>>>
>>>>>>>> I don't think the images are licensed compatibly with GPL. For
>>>>>>>> example:
>>>>>>>>
>>>>>>>>
>>>>>>>>    - *You may not use Images for* pornographic, unlawful or other
>>>>>>>>    immoral purposes, or in a way that can give a bad name to depicted persons,
>>>>>>>>    or to imply endorsement of products and services by identifiable persons,
>>>>>>>>    brands, organisations, etc.
>>>>>>>>    - You are not allowed to mass download Images with an
>>>>>>>>    application, *or reuse a big part of the Images for
>>>>>>>>    redistribution on a similar Website*.
>>>>>>>>
>>>>>>>>
>>>>>>>> Neither of these terms is GPL-compatible.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Jun 5, 2014 at 7:39 AM, Chip Bennett <chip at chipbennett.net>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> What is the license of the specific image?
>>>>>>>>>
>>>>>>>>> If you don't know, then you can't use it.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jun 5, 2014 at 7:38 AM, rose tail <
>>>>>>>>> metallicarosetail at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Can image be used from pixabay or not ?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>  On Thu, Jun 5, 2014 at 4:34 PM, Bryan Hadaway <
>>>>>>>>>> bhadaway at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Unfortunately, that's always a possibility and it absolutely
>>>>>>>>>>> happens.
>>>>>>>>>>>
>>>>>>>>>>> Someone might rip off someone else's work or otherwise infringe
>>>>>>>>>>> and upload or re-release something under their claim of ownership or a new
>>>>>>>>>>> license, then anyone else that uses that work or even promotes it, shares
>>>>>>>>>>> it with others, ends up inadvertently and ignorantly violating the original
>>>>>>>>>>> owner's rights.
>>>>>>>>>>>
>>>>>>>>>>> All we can do is navigate the sometimes tricky world of
>>>>>>>>>>> trademark and copyright law and respect other's rights as much as we can,
>>>>>>>>>>> with the information we have, be kind to one another, in other words, be
>>>>>>>>>>> mature adults and just use our common sense.
>>>>>>>>>>>
>>>>>>>>>>> Then, if one day you get a legitimate cease and desist email
>>>>>>>>>>> (which sometimes is just as unfortunate for the person that has to send out
>>>>>>>>>>> such notices in the first place as it is for you to receive them), there's
>>>>>>>>>>> no reason to be scared or get defensive, you should simply apologize, let
>>>>>>>>>>> them know that you had no idea you were violating their rights and work to
>>>>>>>>>>> quickly and amicably resolve the issue. I'd say 9/10 times, that's all
>>>>>>>>>>> there is to it.
>>>>>>>>>>>
>>>>>>>>>>> Unfortunately, some people/companies might, on rare occasion,
>>>>>>>>>>> try to seek monetary damages or to censor others whether you knew you were
>>>>>>>>>>> doing anything wrong or not. That's partly what
>>>>>>>>>>> http://www.chillingeffects.org/ is about covering.
>>>>>>>>>>>
>>>>>>>>>>> It's kind of a hope for the best, prepare for the worst type
>>>>>>>>>>> situation. You can hope that everyone always does the right thing, but
>>>>>>>>>>> prepare for the fact that they most inevitably won't.
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>
>>>
>>
>> _______________________________________________
>> 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/20140605/1b576b4c/attachment-0001.html>