Chris, this is about the project name, right? I.e. it says we have to call
it "Apache Mesos" in text. I don't see anything about the Apache Software
Foundation logo, which I assume is the feather logo, right?

Open Office seems to get this right with the text for their project name in
their logo http://www.openoffice.org/

On Fri, Jun 28, 2013 at 3:58 PM, Mattmann, Chris A (398J) <
[email protected]> wrote:

> Hi Dave,
>
> I personally think it's a requirement and also specified here:
>
> http://www.apache.org/foundation/marks/pmcs.html#websites
>
>
> The primary branding for any project or product name must be in the form
> of "Apache Foo". This ensures that the project or product is associated
> with the ASF and the project in the minds of our users. The first and most
> prominent reference to a project or product on each page must use the
> "Apache Foo" form of its name. Other references may use either "Apache
> Foo" or "Foo" as appropriate for the subject matter.
>
>
> This falls into the "first and most prominent reference" part. Regardless
> of if they are requirements or not I won't get in to, but from my seat
> as someone who cares about Mesos, but also about the ASF, I think we need
> to make sure there is a prominent first mention of *Apache* Mesos, and
> I read things (as an English language speaker) left to right.
>
> Cheers,
> Chris
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: [email protected]
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
> -----Original Message-----
> From: Dave Lester <[email protected]>
> Reply-To: "[email protected]" <[email protected]
> >
> Date: Friday, June 28, 2013 2:37 PM
> To: "[email protected]" <[email protected]>
> Cc: "[email protected]" <[email protected]>
> Subject: Re: Mesos website refresh process, thoughts, and draft website
>
> >Hey Chris,
> >
> >I didn't see this as a requirement. In general, I think it would be fairly
> >confusing to display the Apache feather logo in the upper left,
> >particularly because the conventions of web design today typically
> >position
> >a project's logo in that corner.
> >
> >Dave
> >
> >
> >On Fri, Jun 28, 2013 at 12:41 PM, Mattmann, Chris A (398J) <
> >[email protected]> wrote:
> >
> >> I love it!!
> >>
> >> One small nit is that in the upper left somewhere, displayed prominently
> >> there should be an Apache Software Foundation logo too.
> >>
> >> Looking styley!
> >>
> >> Cheers,
> >> Chris
> >>
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Chris Mattmann, Ph.D.
> >> Senior Computer Scientist
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 171-266B, Mailstop: 171-246
> >> Email: [email protected]
> >> WWW:  http://sunset.usc.edu/~mattmann/
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Adjunct Assistant Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Dave Lester <[email protected]>
> >> Reply-To: "[email protected]"
> >> <[email protected]>, "[email protected]"
> >> <[email protected]>
> >> Date: Tuesday, June 25, 2013 4:17 PM
> >> To: "[email protected]" <[email protected]>
> >> Subject: Mesos website refresh process, thoughts, and draft website
> >>
> >> >Hi All,
> >> >
> >> >I've expressed an interest in helping with a website refresh, and
> >>wanted
> >> >to
> >> >break this down via email to get some feedback.
> >> >
> >> >*PROCESS*
> >> >It'd be great to embrace an iterative process for the website; the
> >>site is
> >> >never 'done' and I think there are a number of changes we could make
> >>both
> >> >small and large. Shipping smaller changes quickly (especially since
> >> >graduating + more eyeballs) is best, IMHO.
> >> >
> >> >I've created a new Jira issue where you can track this and leave
> >>comments:
> >> >https://issues.apache.org/jira/browse/MESOS-528
> >> >
> >> >*CHANGES*
> >> >There are a number of changes that I'd like to see to the site, in
> >>order
> >> >from "must have" to "nice to have":
> >> > * Add required links to Mesos website:
> >> >https://issues.apache.org/jira/browse/MESOS-66
> >> > * Update the website to use new Mesos logo.
> >> > * Some visual changes to update the overall design of the site, which
> >>is
> >> >a
> >> >bit dated...
> >> > * Making it easier for people to get started with Mesos by simplifying
> >> >and
> >> >updating the site navigation to include 'getting started' and 'getting
> >> >involved.' Probably moving research and FAQ to the documentation.
> >> > * Making it easy to find out who uses Mesos and why by adding a list
> >>of
> >> >active users to the homepage with logos. Testimonials could also be a
> >>way
> >> >for people understand who is using the project and why.
> >> > * Revamping of documentation (see
> >> >https://issues.apache.org/jira/browse/MESOS-511), a few issues are
> >>there
> >> >and I think there is a lot of work that can be done there.
> >> > * Migrate website to a template system of some kind.
> >> >https://issues.apache.org/jira/browse/MESOS-495
> >> >
> >> >*DRAFT Site*
> >> >With some help from Chris A, I've created a mockup of a Mesos website
> >> >refresh that I've shared with a few of you already:
> >> >http://twitter.github.io/mesos-mockup/index.html
> >> >
> >> >Note several things: some of the links don't work; this was just a flat
> >> >site that was created to illustrate some larger ideas. Feedback, both
> >>at a
> >> >high and granular level is appreciated.
> >> >
> >> >*TIMELINE*
> >> >I'd like to see some initial changes made in the next two weeks.
> >> >
> >> >Best,
> >> >Dave
> >>
> >>
>
>

Reply via email to