commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Sanders" <ssand...@nextance.com>
Subject RE: [VOTE] Addition to the Commons charter: coding conventions ( Take 3)
Date Wed, 21 Aug 2002 16:00:12 GMT
+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 <martin.cooper@tumbleweed.com>
> 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:
> > <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:commons-dev-help@jakarta.apache.org>
> > 
> 
> 
> =====
> 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:   
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> For 
> additional commands, 
> e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 
> 

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message