search

jupyter / design

Design related materials for Project Jupyter
BSD 3-Clause "New" or "Revised" License
80 stars 59 forks source link

Licenses for the logo? #47

Open choldgraf opened 6 years ago

choldgraf commented 6 years ago

Hey all - do we have any particular license for the Jupyter logo that's different from the codebase? I think we need to include this with the Binder blogpost. Maybe one of @ellisonbg @fperez would know?

ellisonbg commented 6 years ago

I haven't thought about the license of the actual files, but we do now have a formal trademark that will probably be important to handle properly. Our attorney has given us a list of recommendations that we need to look through about that aspect of the logo. Will probably require a few modifications of our brand guide and IP policy. My initial thought is that our source files (vector drawn) should have a source code style license (BSD two clause), but I am open to a CC style license as well. Thoughts?

On Fri, Nov 24, 2017 at 11:57 AM, Chris Holdgraf notifications@github.com wrote:

Hey all - do we have any particular license for the Jupyter logo that's different from the codebase? I think we need to include this with the Binder blogpost. Maybe one of @ellisonbg https://github.com/ellisonbg @fperez https://github.com/fperez would know?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/design/issues/47, or mute the thread https://github.com/notifications/unsubscribe-auth/AABr0IO-azv0MQs78bS0A65EwolFflN6ks5s5xGdgaJpZM4QqHko .

-- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub bgranger@calpoly.edu and ellisonbg@gmail.com

Carreau commented 6 years ago

I think here the question is attribution, is there any attribution lines for the artwork containing Jupyter+Binder Logo at the top of the elife blog post. I'm going to guess Jeremy did the Binder Logo so it sup to him to say about it.I believe in this case it is faire use (https://www.upcounsel.com/permission-to-use-logo):

A logo or trademark is any photograph, word, or symbol used to identify a brand, service, or product. You need permission to use a logo unless it is for editorial or information purposes, such as when a logo is used in a written article or being used as part of a comparative product statement.

So for eLife no attribution is necessary. I'm willing to say that now and the eLife does not need to write any attribution (pretty obvious as the image are just the two logos) to move forward otherwise the post will not be published, and discuss details after.

npscience commented 6 years ago

Hello, it's absolutely fine on our end to not include any attribution if that is what is ok with everyone. I'll remove the credit line, unless anyone objects by November 29. Thanks!

ellisonbg commented 6 years ago

I think I misunderstood the question - yes this usage falls within our standard Trademark policy:

https://github.com/jupyter/governance/blob/master/trademarks.md

and requires no permission or attribution.

On Sun, Nov 26, 2017 at 3:06 PM, Matthias Bussonnier < notifications@github.com> wrote:

I think here the question is attribution, is there any attribution lines for the artwork containing Jupyter+Binder Logo at the top of the elife blog post. I'm going to guess Jeremy did the Binder Logo so it sup to him to say about it.I believe in this case it is faire use ( https://www.upcounsel.com/permission-to-use-logo):

A logo or trademark is any photograph, word, or symbol used to identify a brand, service, or product. You need permission to use a logo unless it is for editorial or information purposes, such as when a logo is used in a written article or being used as part of a comparative product statement.

So for eLife no attribution is necessary. I'm willing to say that now and the eLife does not need to write any attribution (pretty obvious as the image are just the two logos) to move forward otherwise the post will not be published, and discuss details after.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/design/issues/47#issuecomment-347042379, or mute the thread https://github.com/notifications/unsubscribe-auth/AABr0Biul4S-srwuCUG85sAYLi9eLeKmks5s6eDngaJpZM4QqHko .

-- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub bgranger@calpoly.edu and ellisonbg@gmail.com

choldgraf commented 6 years ago

Good clarification @carreau and thanks for the info @npscience. Shall I close this or do we want to leave it for something to be codified in the documentation?