Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 39633 invoked from network); 21 Aug 2002 16:03:02 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Aug 2002 16:03:02 -0000 Received: (qmail 11282 invoked by uid 97); 21 Aug 2002 16:03:28 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 11262 invoked by uid 97); 21 Aug 2002 16:03:28 -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 11250 invoked by uid 98); 21 Aug 2002 16:03:27 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Subject: RE: [VOTE] Addition to the Commons charter: coding conventions ( Take 3) From: John Keyes To: Jakarta Commons Developers List In-Reply-To: <458473676F1AC74A84EAB2F22004DA6D531111@mail.nextance.com> References: <458473676F1AC74A84EAB2F22004DA6D531111@mail.nextance.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8.99 Date: 21 Aug 2002 16:59:04 +0100 Message-Id: <1029945556.23978.52.camel@oasis> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N +1 for the addition. I wonder is it reasonable to expect each project to have a checkstyle.properties (or at least reference one). This would implicitly state the style. -John K On Wed, 2002-08-21 at 17:00, Scott Sanders wrote: > +1. > > How do we make sure existing projects add 2.2 to their PROPOSAL? > > Scott > > > -----Original Message----- > > From: Morgan Delagrange [mailto:mdelagra@yahoo.com] > > Sent: Wednesday, August 21, 2002 8:31 AM > > To: Jakarta Commons Developers List > > Subject: Re: [VOTE] Addition to the Commons charter: coding > > conventions ( Take 3) > > > > > > +1 > > > > --- 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 and > > > cast their votes. > > > > > > > > > John McNally brought up a good point about the > > > location of the coding > > > convention specification. Here's a slightly amended > > > proposal which takes > > > that into account. > > > > > > > > > From the various threads on this subject, I feel > > > that we've more or less > > > reached informal concensus, so I'd like to make a > > > concrete proposal and call > > > for a vote. > > > > > > I propose to make the following changes to the > > > Guidelines section of the > > > Commons charter: > > > > > > 1) Replace the 3rd sentence of item 17 with the > > > following: > > > > > > --------------- > > > Proposals are to identify the rationale for the > > > package, its scope, its > > > interaction with other packages and products, the > > > Commons resources, if any, > > > to be created, the initial source from which the > > > package is to be created, > > > the coding conventions used for the package (if > > > different from the Sun > > > coding conventions), and the initial set of > > > committers. > > > --------------- > > > > > > The only change here is the addition of the item > > > about coding conventions. > > > > > > 2) After the current item 20 (which is about the CVS > > > repository): > > > > > > --------------- > > > 21. Each Commons component should use an internally consistent and > > > documented coding style. When the source code for a > > > component originates in > > > 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. > > > --------------- > > > > > > (Acknowledgements to Morgan for most of this > > > wording.) > > > > > > In addition, I propose the following addition to the > > > Example Package > > > Proposal of the charter: > > > > > > --------------- > > > (2.2) identify the coding conventions for this > > > package > > > > > > The code uses the conventions from the Jakarta > > > Turbine package. > > > --------------- > > > > > > The above changes have my +1. > > > > > > -- > > > Martin Cooper > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > > > > For additional commands, e-mail: > > > > > > > > > > > > ===== > > Morgan Delagrange > > http://jakarta.apache.org/taglibs > > http://jakarta.apache.org/commons > http://axion.tigris.org > > http://jakarta.apache.org/watchdog > > > > > > > > __________________________________________________ > > Do You Yahoo!? > > HotJobs - Search Thousands of New Jobs > > http://www.hotjobs.com > > > > -- > > To unsubscribe, e-mail: > > unsubscribe@jakarta.apache.org> > > For > > additional commands, > > e-mail: > > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: