[Inpycon] PyCon 2017 Designs from web chirpy

[Vidyadhar Sharma]

Yes. That is correct. The third one is infact sufficiently different, while
the first two are just change in colors. In any case, permission can be
taken.

On Wed 26 Apr, 2017 11:28 pm Abhaya Agarwal, <abhaya.agarwal at gmail.com>
wrote:

> On Wed, Apr 26, 2017 at 9:14 PM, Vidyadhar Sharma <justvidyadhar at gmail.com
> > wrote:
>
>> I just went through the trademark terms. Quoting it, mainly on 'derived
>> logos',
>>
>> "Use of derived logos for user groups and conferences -- Allowed if used
>> to refer to the Python programming language. Commercial user groups and
>> for-profit conferences require permission from the PSF."
>>
>> Since Pycon is a non-commercial event, it is totally fine to use the
>> third logo. And to have no problems, we can just drop a mail to the PSF
>> regarding this. I don't think PSF will have a problem with that.
>>
> The part you quoted is supplementary to the first point which states:
>
> *Derived logos must always be sufficiently different from the Python logos
>> to allow the community to tell the difference.* For example, if you want
>> to create a derived logo for a local Python user group, you might be able
>> to insert an unaltered Python logo graphic into the local group's name in a
>> way that does not cause confusion. But confusingly similar derived logos
>> are not allowed. This includes entwining Python logos with other logos, or
>> connecting them together in a confusing manner. *Logos that simply
>> change the colors or fonts require permission from the PSF Trademarks
>> Committee.*
>
>
> Highlights are mine and they indicate that it might be better to seek the
> permission first.
>
> Regards,
> Abhaya
>
> _______________________________________________
> Inpycon mailing list
> Inpycon at python.org
> https://mail.python.org/mailman/listinfo/inpycon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/inpycon/attachments/20170427/7bb2163b/attachment.html>