Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 32232 invoked from network); 26 Jun 2006 18:57:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Jun 2006 18:57:59 -0000 Received: (qmail 59549 invoked by uid 500); 26 Jun 2006 18:57:57 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 59189 invoked by uid 500); 26 Jun 2006 18:57:55 -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 59178 invoked by uid 99); 26 Jun 2006 18:57:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2006 11:57:55 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of justin.erenkrantz@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jun 2006 11:57:54 -0700 Received: by ug-out-1314.google.com with SMTP id q2so1543791uge for ; Mon, 26 Jun 2006 11:57:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=Da+qp/KmlYkaW7NX37/tOp1n1Wr88PfMbdEqbT1xL0OV7Xy8kZCzh+RfqE2cevCCtw6mxdOdHToUSNZltXN5NBBs3dVizZmXrtpW/ipQdJQ0KgXEt6TKQxCvboLnvVtQgBcUTMxz4fsf8FSquMAjRiz/ZlBeLiDwkzQlZP3YLnI= Received: by 10.67.29.12 with SMTP id g12mr5279999ugj; Mon, 26 Jun 2006 11:57:32 -0700 (PDT) Received: by 10.66.248.3 with HTTP; Mon, 26 Jun 2006 11:57:32 -0700 (PDT) Message-ID: <5c902b9e0606261157w65b3dd8cyb92503d391d7e49c@mail.gmail.com> Date: Mon, 26 Jun 2006 19:57:32 +0100 From: "Justin Erenkrantz" Sender: justin.erenkrantz@gmail.com To: general@incubator.apache.org Subject: Branding of Incubator projects MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 3ec1ada483306a78 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N So, the guide that I'm "tackling" is the "Podling Branding" guide. Here's what I'm proposing after some feedback from others here in Dublin: ---- Podlings are, by definition, not yet fully accepted as part of the Apache Software Foundation. Therefore, they are subject to additional branding constraints. 1. The podling MUST be referred to as "Apache " AND mention that the project is under Incubation. Suitable mentions are: - Inclusion of the http://incubator.apache.org/ URL - The statement that "Apache is currently undergoing Incubation at the Apache Software Foundation." These statements only need to be disclosed upon the first reference in a document. 2. Podling web sites MUST include a clear disclaimer on their website and in all documentation (including releases) stating that they are in incubation. Podlings SHOULD use the following text for all disclaimers: ---- is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the . Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. ---- Podlings wishing to use a different disclaimer message MUST have the disclaimer approved by the Incubator PMC prior to use. 3. Podlings websites SHOULD contain the Apache Incubator Project logo as sign of affiliation. 4. Podlings MUST coordinate with the Apache PRC on all publicity activities by a podling. 5. Until the Incubator PMC approves a podling proposal *and* the podling initial drop code is in our source code repositories, a project or any affiliated persons SHOULD NOT issue any 'press releases' or affirmatively seek positive publicity (such as 'seeding news stories') . 6. The Apache PRC SHALL affirmatively and publicly respond to any such inaccurate publicity surrounding podlings. 7. The Incubator PMC MAY consider the termination of a project for violation of these branding guidelines. ---- If no one comes up with a better policy by tomorrow morning Dublin time, that's what the guide is going to say for now. =) Thanks! -- justin --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org