Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 86142 invoked from network); 21 Aug 2002 12:52:34 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Aug 2002 12:52:34 -0000 Received: (qmail 15412 invoked by uid 97); 21 Aug 2002 12:52:41 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 15368 invoked by uid 97); 21 Aug 2002 12:52:40 -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 15336 invoked by uid 98); 21 Aug 2002 12:52:39 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D638C24.50507@apache.org> Date: Wed, 21 Aug 2002 08:48:36 -0400 From: "Michael A. Smith" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [VOTE] Addition to the Commons charter: coding conventions ( Take 3) References: <7382FCA44E27D411BD4A00508BD68F9504BB0B67@pigeon.tumbleweed.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Martin Cooper wrote: > Taking into account Daniel Rall's comment this time. Sorry about all the > changes, but I'd prefer to refine the text before most people read it an > cast their votes. worth another change? > --------------- > 21. Each Commons component should use an internally consistent and > documented coding style. When the source code for a component originates i > a pre-existing code base outside of Commons, the coding style of that code > base may be retained at the discretion of the initial committers. If a > component does not specify its coding style, the Sun Coding Convention > guidelines are assumed. > --------------- I don't think the second sentance is necessary at all. If a code base is being brought from outside commons into commons, then it only makes sense for the initial committers to choose the coding style. They're required by the first sentance to make sure its consistent and that the one they choose is documented. michael -- To unsubscribe, e-mail: For additional commands, e-mail: