Branding Guide clarification ---------------------------- Key: INCUBATOR-65 URL: https://issues.apache.org/jira/browse/INCUBATOR-65 Project: Incubator Issue Type: Improvement Components: site Reporter: Xavier Hanin
As dicussed on the mailing list recently [1] and [2], I think the branding guide would benefit from some clarification and examples. The second link point to the message with what need some clarification IMO. Here is a copy of the message: On 5/23/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > On 5/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote: > > Mmm, it's still not completely clear. Is the phrase "However, the > > Public Relations Committee MUST review any releases by affiliated > > organizations or groups to ensure they comply with these branding > > guidelines." referring to press release announcing the podling only, > > or to all press releases? Since it seems it's not allowed to issue > > press releases announcing the release, I'd think it's for press > > releases that reference the podling. And that's what my article will > > do, reference the podling. > > I think the gist is in the term "Press release". I think a press > release is something other than an article. A press release is > something like "Foo is adopting Apache Ivy in its product line and > providing professional support for it." and send it across the wire, > i.e. an announcement. > > This is of course something different than "This is how you manage > your Java project dependencies using Apache Ivy, currently undergoing > incubation at the Apache Incubator." which is published on > theserverside.com and/or infoq. It makes sense, indeed. But I think it would be nice to have something in the branding guide more clearly understandable. [1] http://www.nabble.com/to-brand-or-not-to-brand--tf3795172.html [2] http://www.nabble.com/Branding-Guide-clarification-%28was-Re%3A-to-brand-or-not-to-brand-%29-tf3802984.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]