Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 84376 invoked from network); 2 Mar 2004 17:19:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Mar 2004 17:19:53 -0000 Received: (qmail 41484 invoked by uid 500); 2 Mar 2004 17:19:43 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 41416 invoked by uid 500); 2 Mar 2004 17:19:42 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 41403 invoked from network); 2 Mar 2004 17:19:42 -0000 Received: from unknown (HELO discursive.com) (63.246.9.6) by daedalus.apache.org with SMTP; 2 Mar 2004 17:19:42 -0000 Received: (qmail 11917 invoked by uid 500); 2 Mar 2004 17:18:54 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Mar 2004 17:18:54 -0000 Date: Tue, 2 Mar 2004 12:18:54 -0500 (EST) From: Tim O'Brien To: Jakarta Commons Developers List Subject: Re: [SANDBOX] policy question (was Re: [VFS][PATCH] make it compile) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 2 Mar 2004, Henri Yandell wrote: > I don't bother to add to the status file as I consider this kind of thing > to be Commons development and not VFS specific stuff. > > It's a bit rude of me, but no one has complained at me yet for barging > into their project to fix some typo or move docs around. I don't consider that rude at all - I consider that right. Too much "turf" in the Commons - I think this is the main reason why projects stagnate. People assume that "somebody else" is taking care of project X - I've found that they usually are not. If there is a project with shotty documentation or typos, the expectation should be that it can be fixed by *anyone* with commit rights. Broken windows should be fixed by whomever has the itch and the karma, if another committer doesn't like a change then -1 it. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org