From dev-return-39961-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Tue Nov 02 15:31:13 2010 Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 80377 invoked from network); 2 Nov 2010 15:31:13 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 15:31:13 -0000 Received: (qmail 90421 invoked by uid 500); 2 Nov 2010 15:31:44 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 90215 invoked by uid 500); 2 Nov 2010 15:31:42 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 90206 invoked by uid 99); 2 Nov 2010 15:31:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 15:31:41 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of t.p.ellison@gmail.com designates 209.85.215.49 as permitted sender) Received: from [209.85.215.49] (HELO mail-ew0-f49.google.com) (209.85.215.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 15:31:32 +0000 Received: by ewy19 with SMTP id 19so3400970ewy.36 for ; Tue, 02 Nov 2010 08:31:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=R0aXbncJAZtEliqxYNI9x1VJLgnM43WmWsF3eoX6hIw=; b=YiHHtDMhmdhi4SwuHEREcAw8aIB7W4pepVFdCEyJv4IZN9fDkzLGniB2oI4pUMWv+g mdEt9TsHyd1i5xze8Ya+l2KAv1RkR/u6eV8PcGOd5N8ymXlnR9qVnUs+MrQZOo+c9xO7 oGstTwVRK5KRsmP0L53PrE/piKQr5jU8uZndE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=iDSngJyU3ZXxpfC0/bvv2dlKI52MoKotltL7TrrZVpslMnXYbCbGiqVa1npkKAPpMY nCPoapErvkpcQq66nXBKmzhsAnUAfCURVKFzDHbJxO9JvHC82c4bq/jfssSsfTCmUyfO /7oeUADjQWtM/xbamz4KWv2oKfvySsJPAYEtk= Received: by 10.213.109.10 with SMTP id h10mr617720ebp.61.1288711872566; Tue, 02 Nov 2010 08:31:12 -0700 (PDT) Received: from [9.20.183.159] (gbibp9ph1--blueice3n2.emea.ibm.com [195.212.29.84]) by mx.google.com with ESMTPS id v51sm5524571eeh.4.2010.11.02.08.31.10 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Nov 2010 08:31:11 -0700 (PDT) Message-ID: <4CD02EC0.3020407@gmail.com> Date: Tue, 02 Nov 2010 15:31:12 +0000 From: Tim Ellison User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: dev@harmony.apache.org Subject: Re: [site] Branding requirements References: <4CBC2187.9090505@gmail.com> In-Reply-To: <4CBC2187.9090505@gmail.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 18/Oct/2010 11:29, Tim Ellison wrote: > All Apache projects have been asked to abide by these foundation-wide > guidelines [1]. > > Having a quick look down the list of things that are expected, it seems > we have a few site patches to make. > > [1] http://www.apache.org/foundation/marks/pmcs Here's a quick to-do based on the Project Branding Board Report Checklist. I can create JIRAs for them if people prefer to take on some tasks. * Project Website Basics : homepage is project.apache.org - All looks ok here. * Project Naming And Descriptions : use proper Apache forms, describe product, etc. - We need to add some simple description in the right form to the homepage and download page. * Website Navigation Links : navbar links included, link to www.apache.org included - All looks ok here. * Trademark Attributions : attribution for all ASF marks included in footers, etc. - We need to add these. * Logos and Graphics : include TM, use consistent product logo on your site - The usage is ok, but seems we need a (TM) on the logo. * Project Metadata : DOAP file checkedin and up to date - we have one here http://projects.apache.org/projects/harmony.html but it needs updating. Regards, Tim