+1 to Chris A.

On the larger issue of conforming with branding guidelines, I'm in complete
agreement that this is important short-term work for the project; I'm happy
to take the lead. I've mocked up of a site refresh that should be fully
compliant with the guidelines (appropriate linking, copyright notices,
etc), and plan to improve and share that sometime next week -- I thought it
was better to focus on pushing through one thing at a time.


On Thu, Jun 20, 2013 at 1:55 PM, Chris Aniszczyk <[email protected]> wrote:

> On Thu, Jun 20, 2013 at 1:48 PM, Mattmann, Chris A (398J) <
> [email protected]> wrote:
>
> > Hi Dave,
> >
> > This is an important one so wanted to follow up here on the dev
> > list (CC to [email protected] so it will go to JIRA too).
> >
> > The logo for Apache Mesos needs to conform to the branding
> > requirements, here:
> >
> > http://www.apache.org/foundation/marks/pmcs
>
>
> The only thing about the branding requirements is that there exists a "TM"
> near the logo... that's it
>
> *Logos And Graphics
>
> Logos are important to recognize as trademarks as well. For the project's
> official logo (if it has one, and especially if it uses the ASF feather),
> ensure that it includes a small "TM" symbol in the graphic or immediately
> adjacent to it. For pages that include the project logo on them, ensure you
> mention "... and the Project logo are trademarks..." in the attribution.
>
> Projects may may choose to use the Apache feather in their logo if they
> wish, but if they do so they should contact trademarks@ to determine the
> best format of the feather to use. In the near future we plan to have much
> simpler versions of the feather to incorporate if desired, including
> various sizes and colors.*
>
> but if you look at other Apache projects... no one does this... Hadoop...
> Pig... Shrio... etc... I think we'll be OK. I think it's really important
> to choose the best logo for the project and then worry about the details.
>
> --
> Cheers,
>
> Chris Aniszczyk | Open Source | Twitter, Inc.
> @cra | +1 512 961 6719
>

Reply via email to