Return-Path: Delivered-To: apmail-community-archive@www.apache.org Received: (qmail 47000 invoked from network); 11 Jul 2007 11:55:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Jul 2007 11:55:13 -0000 Received: (qmail 59069 invoked by uid 500); 11 Jul 2007 11:55:13 -0000 Delivered-To: apmail-community-archive@apache.org Received: (qmail 58678 invoked by uid 500); 11 Jul 2007 11:55:11 -0000 Mailing-List: contact community-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: community@apache.org List-Id: Delivered-To: mailing list community@apache.org Received: (qmail 58656 invoked by uid 99); 11 Jul 2007 11:55:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2007 04:55:11 -0700 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=DNS_FROM_AHBL_RHSBL,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ted.husted@gmail.com designates 64.233.162.224 as permitted sender) Received: from [64.233.162.224] (HELO nz-out-0506.google.com) (64.233.162.224) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2007 04:55:08 -0700 Received: by nz-out-0506.google.com with SMTP id s1so958611nze for ; Wed, 11 Jul 2007 04:54:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=lATFcX0QBrMBAImxqqYIabbXJQmeY5nSvkTxRYSvv9V90cR5jTjUJqvMQd/MeZyXHA9IlyRbIQl8uDaEmYnf5oaSAPJxCkq0lKnt2cOp5S3zlfCmNDpTZMFgEZbM7TUaqlrKU4vsVJrcVslgWOqrf9vRUIVZSZsuIaBL6LE9CFw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=FW1T2vzI45QovkPgcookV7vwXvabqfATLckzRdP86yuE4kj7PbXToJPH6X7wGMoeVUUWBYq2wPS2Q18BGjTyCkAgcVfurLVlbkB1R5iU707OC/O/INMWMPOhFOd3wTgPcSHlhwiNXqO0EwK1s/slqhUvCycB9eZJIgYQlroqA7M= Received: by 10.141.107.13 with SMTP id j13mr1605066rvm.1184154886982; Wed, 11 Jul 2007 04:54:46 -0700 (PDT) Received: by 10.141.201.12 with HTTP; Wed, 11 Jul 2007 04:54:46 -0700 (PDT) Message-ID: <8b3ce3790707110454y3a88af1eu990cfa609f4150f8@mail.gmail.com> Date: Wed, 11 Jul 2007 07:54:46 -0400 From: "Ted Husted" Sender: ted.husted@gmail.com To: community@apache.org Subject: Re: Grassroots PR In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8b3ce3790707040752l67f18c12m949b803874d4402e@mail.gmail.com> X-Google-Sender-Auth: e0e15b8555f7a5a1 X-Virus-Checked: Checked by ClamAV on apache.org On 7/6/07, J Aaron Farr wrote: > Shouldn't PMC Chair's either be (1) willing to respond or (2) able > find someone in their project? This isn't that onerous of a task and > it provides the PRC with a ready made list of contacts. On the PRC list it was suggested that when someone from the media visits one of our sites, it's not clear who to contact with a press inquiry. We purposely funnel all inquiries to the public lists, and someone from the media might not be comfortable posting to a public list. Very few of our project sites mention how to contact us regarding press or security inquiries. It was suggested that many media folks might be discouraged from contacting us at all, and so our perspective is going unheard. In my experience, persistent inquirers do tend to contact one or more committers at random with press or security questions. Perhaps we should at least encourage projects to mention press@ and security@ on the project sites, as we do on the top-level apache.org site. For example, I just updated the Struts FAQ to include how to contacting us regarding security or press inquiries. * http://struts.apache.org/kickstart.html#press -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: community-unsubscribe@apache.org For additional commands, e-mail: community-help@apache.org