tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Sexton" <>
Subject RE: never say never...
Date Tue, 21 Feb 2006 01:18:00 GMT

> -----Original Message-----
> From: Mark Thomas [] 
> Sent: Monday, February 20, 2006 5:33 PM
> To: Tomcat Developers List
> Subject: Re: never say never...
> On the subject of fairness, is it fair that someone who is too lazy to
> read the spec / read the docs / etc should take up any more of the
> community's time than the absolute minimum required to, for example,
> mark the bug as INVALID? This isn't a view I advocate but it is one I
> understand.

OK, let's throw out the whole fairness thing. How can the Tomcat committers
most efficiently, and with the least amount of anger, hate, and discontent
handle people who do not put in a reasonable effort to understand things or
submit reasonable defect reports.

Candidates are:

1)	Committer marks it resolved | invalid. Submitter demands to know
why. Committer re-marks it RESOLVED | INVALID, ad infinitum until some other
committer decides to break the cycle. Nobody's really happy with this.

2)	The committer puts in a minimal reason referencing the spec. To make
most people happy, a reference to the specific portion of the spec would
have to be researched. The user learns nothing, and the committer is
answering questions instead of fixing code.

3)	The committer marks it resolved | invalid, and sends the user to the
ESR paper on "How to ask questions the smart way." Since the committer could
save this snippet of text and copy and paste the text, it seems like it
wouldn't be hard. This would hopefully educate the user and result in higher
quality submissions in the future.

If I've missed any solutions I'd be interested in them.

George Sexton
MH Software, Inc.
Voice: 303 438 9585

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message