[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    Re: Addressing Submissions
From:       "Paul Glezen" <pglezen () us ! ibm ! com>
Date:       2001-05-20 16:33:57
[Download RAW message or body]

I agree.  I don't like to see submissions "fall through the cracks."  But
it's difficult when you have other jobs on top of log4j (like I believe we
all do).  If the submission comes at a particular busy point, you tell
yourself you will get to it later.  When you finally get a block of time to
allocate to log4j, your mailbox has 100+ log4j forum messages in it and the
submission get buried.

Ownership (in the sense of coordinating changes) might help somewhat.  I
like to think that to some extent, this has already happened to some
extent, albiet implicitly.  If someone suggests a change to code I've
written or recently modified, I'll be more included to act on it.  If it is
something I have not had much experience with (like SMTP), I'm more likely
to leave it alone.

- Paul

Paul Glezen
IT Specialist
Software Services
818 539 3321

Anders wrote:

It does seem like quite a few code submissions fall through the cracks
-- maybe because there's no notion of ownership for various parts of the
code (not ownership in the traditional sense, obviously).


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]