tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Ball" <db...@rhoworld.com>
Subject Re: JSPC refactoring/documentation
Date Wed, 13 Nov 2002 15:54:36 GMT
On 11/12/2002 at 4:03 PM Costin Manolache wrote:

>Fredrik Westermarck wrote:
>
>> The problem that I and others have experienced is that proposals and/or
>> patches, by non-committers, don't get discussed or voted about.
>
>You have to keep pushing. If you send patches and proposals you can
>become a committer - and then you'll start ignoring patches and proposals

>:-)

I know you mean that in jest, but I have two big problems with what you
said:

1. Simply sending patches and proposals is enough to become a committer? On
the other apache projects on which I've worked, several months of
consistent quality patches and involvement on the lists is necessary to
achieve committer status.

2. Committers ignore patches and proposals from non-committers - though
said with smilies, does seem to be the status quo, from my personal
experience and that of others. Do you not see this as a problem?

Not every guy who finds (and patches!) a bug in tomcat has the time or
interest to become a committer (nor should they), and I don't think you
should require that before their patches have a chance to get in. I know
that no one ever has enough time to do everything, and staying on top of
patch submissions can be a chore, yes. With enough committers, and tomcat
certainly seems to have enough, you can manage - make it a rotating chore
to scan the developers list, tell patchers that they should contact the
module authors directly, use bugzilla to manage the patch queue, etc.,
etc., etc.

>I'm sorry - but everyone is very short on time. If you have a real
interest
>in tomcat the best solution is to send patches, insist on getting them
>accepted and become a committer. I think many people here will tell you
>it's not that hard.

Therein lies the rub. Not every joe that comes up with a patch for tomcat
should get committer access, in my eyes. Nor should the tomcat developers
ignore contributed patches. There's got to be a better way.

- donald


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message