Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 15368 invoked from network); 23 May 2007 12:28:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 May 2007 12:28:44 -0000 Received: (qmail 45632 invoked by uid 500); 23 May 2007 12:28:44 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 45404 invoked by uid 500); 23 May 2007 12:28:43 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 45313 invoked by uid 99); 23 May 2007 12:28:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 05:28:43 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 05:28:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A34D771403E for ; Wed, 23 May 2007 05:28:16 -0700 (PDT) Message-ID: <600126.1179923296666.JavaMail.jira@brutus> Date: Wed, 23 May 2007 05:28:16 -0700 (PDT) From: "Xavier Hanin (JIRA)" To: general@incubator.apache.org Subject: [jira] Created: (INCUBATOR-65) Branding Guide clarification MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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 wrote: > > On 5/22/07, Xavier Hanin 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: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org