Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Subject: Re: ASF Board Summary for February 18, 2004
From: David Crossley <crossley@apache.org>
To: dev@cocoon.apache.org
In-Reply-To: <403E3429.50807@vafer.org>
References: <20040223041901.B12963@lyra.org> <403A144A.5040602@apache.org>
	 <403A5239.70400@vafer.org> <1077586060.31546.764.camel@ighp>
	 <8FF770D7-669E-11D8-89D5-000A958B684A@outerthought.org>
	 <D7D08070-66FC-11D8-9F8D-000393D2CB02@apache.org>
	 <403E1AD5.5000005@vafer.org>
	 <C37E5664-687D-11D8-90F6-000A958B684A@outerthought.org>
	 <403E3429.50807@vafer.org>
Content-Type: text/plain
Organization: 
Message-Id: <1077838129.31547.2033.camel@ighp>
Mime-Version: 1.0
Date: 27 Feb 2004 10:28:50 +1100
Content-Transfer-Encoding: 7bit

Torsten Curdt wrote:
> Steven Noels wrote:
> > Torsten Curdt wrote:
> > 
> >> + and we remove all author tags
> > 
> > 
> > I find this just a little bit too reactionary - especially for the 
> > little known/used areas of code. We haven't had "ownership issues" 
> > because of them in the past, not? These tags sometimes help to find a 
> > contact, when questions remain unanswered on the list.
> 
> Well, a lot of people gave their +1
> 
> I am far from pushing this - actually I see it exactly like you do.
> 
> ...but IIRC the board explicitly discouraged the author tag and
> we also had a lengthy discussion about this. Since we need to
> update the license anyway, I thought this might be the right time
> to follow the board's advice.

IIRC, when we talked about author tags last time, one of
the main points was that people can look at the "Changes"
page to find out who was the major contributer for a certain
facility and who has been working on it. This is also by far
the best way to give encouragement to the community. We do not
need the author tags in code and docs.

There is an added benefit to this approach. It makes us devs
be more mindful of keeping Changes up-to-date.

--David