[Mesa-dev] New Mesa3D.org website proposal

Eric Engestrom eric at engestrom.ch
Thu May 7 14:49:22 UTC 2020


On Thursday, 2020-05-07 16:26:19 +0200, Erik Faye-Lund wrote:
> On Thu, 2020-05-07 at 16:18 +0200, Eric Engestrom wrote:
> > On Thursday, 2020-05-07 16:07:00 +0200, Erik Faye-Lund wrote:
> > > On Thu, 2020-05-07 at 09:05 -0500, Jason Ekstrand wrote:
> > > > Looks shiny but....
> > > > 
> > > > We need to be very careful here. One of the big no-nos with
> > > > Khronos
> > > > trademark rules is using logos for things where implementations
> > > > aren't
> > > > conformant.  Mesa has been living in a mirky in-between land for
> > > > a
> > > > while and everything has been mostly fine.  We've been very
> > > > careful
> > > > to
> > > > *not* say that Mesa is an implementation of any Khronos APIs.
> > > > Instead, we say that Mesa is an open-source software project that
> > > > contains implementations and that some of those implementations
> > > > are
> > > > conformant.  That page full of logos makes me concerned that
> > > > we're
> > > > going to risk getting into trouble.  Khronos marketing cares A
> > > > LOT
> > > > about logos.
> > > 
> > > As I wrote in the e-mail, I've already clarified the logo-usage
> > > with
> > > Khronos. They are happy with it as-is.
> > 
> > Could you post their concerns/guidelines here, so that we can all
> > know
> > what can and cannot be on the website and make sure we never cross
> > the
> > line with future changes?
> 
> You can find their logo guidelines here:
> https://www.khronos.org/legal/trademarks/
> 
> But because Mesa is in a special eternal conformant/non-conformant
> limbo, I sent an email to clarify. I've posted the response I got here:
> 
> https://gitlab.freedesktop.org/snippets/996
> 
> I think the first link is going to be what most people care about,
> though.

OK, so basically
- make sure we use the up-to-date, unmodified logos from Khronos
- make sure we are clearly stating that the project is not conformant as a whole,
  but as you said only some "combinations of drivers and APIs" are.

I think that should be easy enough to not mess up :)


More information about the mesa-dev mailing list