Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 29259 invoked from network); 16 Jan 2004 19:00:35 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Jan 2004 19:00:35 -0000 Received: (qmail 5905 invoked by uid 500); 16 Jan 2004 19:00:23 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 5834 invoked by uid 500); 16 Jan 2004 19:00:22 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 5820 invoked from network); 16 Jan 2004 19:00:22 -0000 Received: from unknown (HELO umbongo.flamefew.net) (64.253.103.114) by daedalus.apache.org with SMTP; 16 Jan 2004 19:00:22 -0000 Received: by umbongo.flamefew.net (Postfix on Linux (i386), from userid 500) id 7F7311A9F; Fri, 16 Jan 2004 14:00:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by umbongo.flamefew.net (Postfix on Linux (i386)) with ESMTP id 7A76D1A7E for ; Fri, 16 Jan 2004 14:00:21 -0500 (EST) Date: Fri, 16 Jan 2004 14:00:21 -0500 (EST) From: Henri Yandell X-X-Sender: hen@umbongo.flamefew.net To: Jakarta Commons Developers List Subject: Re: [lang] maven site In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Fri, 16 Jan 2004, Tim O'Brien wrote: > On Fri, 16 Jan 2004, Henri Yandell wrote: > > The solution I think is to change the Commons site utterly. Stop it being > > an umbrella site, and turn it into more of a portal. Something that lists > > the site but doesn't have any need for a change to the portal page to > > imply a change to all sub-pages [beyond a change of logo]. > > I hear what you are saying on one level, but I don't think that this issue > is completely unsolvable. I think we need to make a three month plan with > some milestones, and talk about a unified rendering strategy. In the > short-term I think unified Navigation would be a straightforward thing to > do with our current setup, and I'm willing to put in the time (and donate > my own hardware) resources for testing out some strategies. > > I'll put together a proposal about how Commons should approach site gen. Sounds good. This is the best way to handle such touchy issues as a common way to handle all projects I think. Is Wiki a good place to draft your proposal? [Personally I liked my xslt toy stuff to put maven projects into categories *grin*] Hen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org