Return-Path: Delivered-To: apmail-community-archive@www.apache.org Received: (qmail 79835 invoked from network); 4 Jul 2007 14:52:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jul 2007 14:52:48 -0000 Received: (qmail 21437 invoked by uid 500); 4 Jul 2007 14:52:48 -0000 Delivered-To: apmail-community-archive@apache.org Received: (qmail 21160 invoked by uid 500); 4 Jul 2007 14:52:47 -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 21149 invoked by uid 99); 4 Jul 2007 14:52:47 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2007 07:52:47 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ted.husted@gmail.com designates 64.233.162.229 as permitted sender) Received: from [64.233.162.229] (HELO nz-out-0506.google.com) (64.233.162.229) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2007 07:52:43 -0700 Received: by nz-out-0506.google.com with SMTP id i1so1413088nzh for ; Wed, 04 Jul 2007 07:52:22 -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:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=P/6FcY0bfRRZ7KyqKvkKBTSm5GPrEdpEp2x+BYKQpTN/MTzHQYdVbayqed3rMteoGelnDBCGYdmjELbKfZPBq9kzTj6bn54O25fEYJ6YPzuhE3J4Z8rAO0mtJNeX7FlMe3v0SjH1stxBAsnGxl3BtQz3nJke+EsK0jMeEgTrVvA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=mMFbCfGU9zJuvzolS3PvF15TTLT4Vbj6J9DGa7o9yldiLHnexCDjIDklLxY/HzGfA8yjjYAiFQHlsbKingoVksUrM17cRYtsPGVhCryIetSSKY7Ow8KuaRWWdp4uI1BvnwHibSPZ5esaZsR2E1YqzTVCkpVQYH42PPTSpYRKpG0= Received: by 10.140.186.18 with SMTP id j18mr2072026rvf.1183560742098; Wed, 04 Jul 2007 07:52:22 -0700 (PDT) Received: by 10.141.201.12 with HTTP; Wed, 4 Jul 2007 07:52:22 -0700 (PDT) Message-ID: <8b3ce3790707040752l67f18c12m949b803874d4402e@mail.gmail.com> Date: Wed, 4 Jul 2007 10:52:22 -0400 From: "Ted Husted" Sender: ted.husted@gmail.com To: community@apache.org Subject: Grassroots PR 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: 90523295fc3693b1 X-Virus-Checked: Checked by ClamAV on apache.org (Note that a draft of this message was posted to PRC@ before posting here.) In recent threads on the PRC list, a couple of items came up that might be worth bringing to the community for further discussion. These suggestion all require community participation, and so a key question is whether the community would participate :) * Extending people.apache.org with personal profiles * press@project and security@project email drops * A Roller zone for PMC blogs Extending people.apache.org with personal profiles It's been suggested that we circulate a press release regarding the election of the 2007-2008 board, and include some headshots and bios of present and past officers and board members on our board page. We've started to collect more information about the people involved in the foundation at , but the site is not well publicized. If we would like to post profiles of our board members, perhaps we would also like work toward providing personal profiles for all of our committers. If we added personal profiles to the people.apache.org site, and added the capability to create a page per ASF project or group, we might end up with "Who we are" pages for each project that looked something like the profile page here: . For discussion purposes, I've posted an example of an ASF personal profile at , cribbing from the Debian site. Again, the format is for discussion purposes only. Should we encourage a more personal touch to our "who we are" pages? press@project and security@project email drops A recurring PR problem is finding someone with product knowledge to contact that's willing to respond. Perhaps we should encourage all projects to setup individual press@ and security@ mail drops that could go to people within the project, who could then forward valid messages to private@. Of course, it makes no sense to setup a project press@ drop unless there are volunteers in the project willing to do the work. If a project were up to handle its own press@, we could also copy press@apache.org, so that there is some central oversight. Should we encourage per-project press@ and project@ mail drops? A Roller zone for PMC blogs One of the most popular blogging softwares on the planet, Roller, is now an ASF project . Perhaps it's time to eat our own dogfood and encourage development of a Roller zone where our PMC's can post easy-to-aggregate announcement blogs. These would not be individual blogs as we have on PlanetApache.org, but PMC blogs that would focus solely on project news. The initiative could be tied to , so that there was a one-stop shop for project news. Aside from Roller, another way to go would be an XML-based feed, like the one that's being used at Jakarta. As always, the tipping point would be whether we have volunteers up to doing the work. Should we encourage projects blogs to post and aggregate project news and events? If the community is interested in doing more to publicize the foundation's activities, I'm sure there are other things we could do as well. Of course, a key question is whether we want to raise our our profile or just be the quiet juggernaut. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: community-unsubscribe@apache.org For additional commands, e-mail: community-help@apache.org