Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 46899 invoked by uid 500); 29 May 2002 15:25:23 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 46841 invoked from network); 29 May 2002 15:25:23 -0000 Subject: RE: too many "inactive" committers To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Glyn Normington" Date: Wed, 29 May 2002 16:21:33 +0100 X-MIMETrack: Serialize by Router on d06ml007/06/M/IBM(Release 5.0.9a |January 7, 2002) at 29/05/2002 16:25:21 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >Perhaps reviewing the submissions and -1'ing them would be better than >to keep silent. Otherwise, contributing has no sense, and people give up. >This is the fourth case that I'm aware of in axis-dev. People giving up *really* gets to me, especially as I must take partial responsibility. Not only is Axis the worse, but the people involved presumably go away feeling their contributions were unwanted, which is a great shame. I'd like to play my part in fixing this, but since Axis is the first open source project I've worked on, I'm still learning the ropes. What should I do when someone sends in a plausible patch in an area that's unfamiliar to me but the other commiters appear to ignore it? Should I vote +1 and if there are another two positive votes, take that as a mandate to commit the change? I guess the problem is I'm hesitant to change code that I don't personally understand well, so I tend to leave this to the experts in a particular area, even though they may be too busy. Do I need to have thoroughly understood any change I commit or is it reasonable to put some trust in the submitter of the change? On a slightly different tack, I was approached on two separate occasions with offers of help to implement the JAXM SOAP interfaces, but when I explained how to make a start, I heard nothing more. Perhaps newcomers worry about communicating openly on axis-dev? How can we cut through the mystique and let newcomers know that the rest of us are just ordinary programmers doing our best, understanding some things but not everything, and occasionally messing up and helping each other fix things up? For some reason, just saying this doesn't seem enough. Glyn