Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention that the logo are intended to be free for use #132

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

joker-eph
Copy link
Contributor

Should we adopt an actual license?

Should we adopt an actual license?
@marbre
Copy link
Member

marbre commented Feb 1, 2023

Thanks for filling the issue @joker-eph. I would be awesome to clarify in which way the logos can be used, amongst other things for my presentation in the LLVM devroom at FOSDEM.

@jpienaar
Copy link
Member

jpienaar commented Feb 1, 2023

I think we should ask Tanya if there is one we can use yes. Looking at other projects they have phrases such as "use when accurately referring to MLIR or MLIR project". This world is a. It outside my normal expertise :-)

@lattner
Copy link

lattner commented Feb 1, 2023

It would also be great to add it to https://llvm.org/Logo.html

@joker-eph
Copy link
Contributor Author

It would also be great to add it to https://llvm.org/Logo.html

What do you refer to in "add it"? The MLIR Logo or a license?

The page you link has:

This dragon image is owned by Apple Inc. and is available for your download and use royalty-free. By downloading this image, Apple grants you, and you accept, a non-exclusive license to use this image. All right, title and interest in the image, including the copyright therein, is retained by Apple.

We can add another section for MLIR later in the page?

In any case I need input on how to frame the intended usage / license the foundation wants to grant for the MLIR logo.

@lattner
Copy link

lattner commented Feb 1, 2023

I mean both, it looks like the Logo page needs better guidance on usage overall. I'm just saying that MLIR is part of LLVM and so all the relevant LLVM'y logos can be hosted on one page (+ other more specialized ones as well of course)

@joker-eph
Copy link
Contributor Author

Makes sense, I'll update https://llvm.org/Logo.html when we have a blurb. I'll wait to see how @tlattner propose we formulate this :)

@tlattner
Copy link

tlattner commented Feb 4, 2023

Yes, we should have a license and trademark usage on our website. This is not going to be a quick addition (and has been on my TODO list awhile). Are you asking for a simple approval for some use or wanting the proper solution to be done?

@joker-eph
Copy link
Contributor Author

Up-to-you how you want to take it: it there some language we can add now pending a proper license?

@joker-eph
Copy link
Contributor Author

joker-eph commented Apr 10, 2023

@marbre
Copy link
Member

marbre commented Sep 7, 2023

Any update on this?

@joker-eph
Copy link
Contributor Author

Let's try to address it at the dev meeting next month!

Copy link
Member

@jpienaar jpienaar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know how logo licenses look unfortunately 🙂 I think there is normally some clause to avoid being used in a way that could be construed as product endorsement (not that I see that as being a big issue here, but if there is some standard good approach ...)

@marbre
Copy link
Member

marbre commented Sep 24, 2023

I think something like for the C++ logo would be desirable (https://isocpp.org/home/terms-of-use):

The “Standard C++ Foundation” name and stylized “C++” logo are trademarks of the Standard C++ Foundation and may not be used without permission from the Foundation. Permission is hereby granted:

  • to use the unaltered logo in conjunction with any product (including but not limited to a C++ compiler implementation or tool, or a product written using C++) or material (including but not limited to product packaging, documentation, educational material, user group meeting information, or blog post) that is related to the standardized C++ language or working drafts thereof (including the C++ International Standard and related Technical Specifications, whether published or draft, but excluding nonstandard vendor-specific extensions), and that does not imply endorsement of a product or organization (including but not limited to that it is not being used as part of another organization’s logo); and
    [..]

In general, we want the logo to be used as widely as possible to indicate material related to the portable C++ and its applications, without implicitly endorsing something or someone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants