Return-Path: Mailing-List: contact community-help@apache.org; run by ezmlm Delivered-To: mailing list community@apache.org Received: (qmail 34687 invoked from network); 1 Dec 2002 18:50:41 -0000 Received: from i.meepzor.com (HELO Boron.MeepZor.Com) (204.146.167.214) by daedalus.apache.org with SMTP; 1 Dec 2002 18:50:41 -0000 Received: from Golux.Com (dsl-64-192-128-105.telocity.com [64.192.128.105]) by Boron.MeepZor.Com (8.11.6/8.11.6) with ESMTP id gB1IojY20537; Sun, 1 Dec 2002 13:50:45 -0500 Message-ID: <3DEA5A0D.9C9927D@Golux.Com> Date: Sun, 01 Dec 2002 13:50:53 -0500 From: Rodent of Unusual Size Organization: The Apache Software Foundation X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: community@apache.org Subject: Re: [proposal] creation of communitity.apache.org References: <3DEA5498.2020404@apache.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "Andrew C. Oliver" wrote: > > If Ken puts a little more description on the page, the keywords should > get picked up by google. My blog seems to be well regarded by google. i'd rather address the issue of those people who use their directories for non-about-me stuff first.. there. anyone who *doesn't* want their cvs.apache.org/~name/ directory listed can simply create an empty ~/public_html/.nopublish file, and the script won't include them. as for beefing up the page.. i might do that, but publishing it anywhere generally visible should wait until the people being listed on it have consented. considering that.. making this an opt-in by checking for a .publish file might be a better approach. that way, anyone who wants to be listed has to take an explicit step to make it happen, rather than being listed without necessarily even knowing about it. if this becomes the basis of a genuinely public page, something along those lines will be a requirement. as long as it's private, though, i don't mind keeping it opt-out rather than opt-in.