Return-Path: 
 <forrest-dev-return-6743-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 63471 invoked by uid 500); 23 Aug 2003 07:43:27 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 63244 invoked from network); 23 Aug 2003 07:43:22 -0000
Received: from grunt25.ihug.com.au (203.109.249.145)
  by daedalus.apache.org with SMTP; 23 Aug 2003 07:43:22 -0000
Received: from p401-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.141.147]
	by grunt25.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19qT3W-0006Dp-00; Sat, 23 Aug 2003 17:43:27 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19qT3y-0001IG-00
	for <forrest-dev@xml.apache.org>; Sat, 23 Aug 2003 17:43:54 +1000
Date: Sat, 23 Aug 2003 17:43:54 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: [patch] person tag
Message-ID: <20030823074354.GA2418@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <1060954000.3f3cdf904c572@secure.solidusdesign.com>
 <1061599060.3f46b754bf161@secure.solidusdesign.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1061599060.3f46b754bf161@secure.solidusdesign.com>
User-Agent: Mutt/1.5.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Fri, Aug 22, 2003 at 08:37:40PM -0400, Dave Brondsema wrote:
> 
> Hello?  The lack of response to some of my posts here, and for other OS projects 
> is frustrating.  Especially when what I'm posting is a patch, hopefully 
> something to improve the project.  What does it mean when nobody responds?

It means it bypassed people's radars the first time, and a reminder email
should be sent.  Bigger projects use bugtrackers to ensure patches don't
get lost.  Perhaps we should too.

In this case, I didn't respond because I'm not sure if the patch is a
good idea, and wanted time to think/hear people's opinions.  A page with
a mailto: link to the author implies that the author should be contacted
for comments/changes.  That is not the case in ASF projects, where
authorship does not equal ownership.  If anything, I'd like to go the
other way; make the appearance of *any* accreditation on the web page
optional.  What do people think?

> You don't care?
> You're too busy?
> This patch doesn't work?
> You don't like me?
> This patch isn't even wanted?
> 
> I'd fork forrest right now, just so I could do commits.  But obviously that 
> wouldn't be good in the long run, since eventually my changes would be drastic 
> enought that I couldn't merge mainline changes into mine.

In Forrest, almost everything can be overridden in the project itself, so
modifying Forrest isn't necessary.  For instance, modified skin
stylesheets can be put in
$PROJECT/src/documentation/skins/@skin@/xslt/html


--Jeff

> -- 
> Dave Brondsema
> 
> 
> Quoting Dave Brondsema <dave@brondsema.net>:
> > 
> > This patch takes advantage of the @email attribute on the <person> tag.  It
> > respects the obfuscate-email-links setting, too.
> > 
> > This is just for 'common', but it should be trivial to apply to the change
> > to
> > any skins that need it.
> > 
>