You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Martin Cooper <ma...@tumbleweed.com> on 2002/08/21 06:58:08 UTC
[VOTE] Addition to the Commons charter: coding conventions
>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 add the following to the Guidelines section of the Commons
charter, 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 should be retained. If a component does not specify its coding style,
the Sun Coding Convention guidelines are assumed.
---------------
(Acknowledgements to Morgan for most of this wording.)
This has my +1.
--
Martin Cooper
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Addition to the Commons charter: coding conventions
Posted by Jeff Dever <js...@sympatico.ca>.
And what about checkstyle? Developers that submit to various different projects
will have difficulty adhering to several "internaly consistant" coding styles.
Having software support for this would at least make the process of contributing
consistant, and would increase the chances of those coding styles being adhered
to.
Checkstyle should be at least reccomended in the charter (perhaps maven as well).
John McNally wrote:
> Should the location of any coding convention specification be
> standardized?
>
> john mcnally
>
> On Tue, 2002-08-20 at 21:58, Martin Cooper wrote:
> > >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 add the following to the Guidelines section of the Commons
> > charter, 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 should be retained. If a component does not specify its coding style,
> > the Sun Coding Convention guidelines are assumed.
> > ---------------
> >
> > (Acknowledgements to Morgan for most of this wording.)
> >
> > This has my +1.
> >
> > --
> > Martin Cooper
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [VOTE] Addition to the Commons charter: coding conventions
Posted by John McNally <jm...@collab.net>.
Should the location of any coding convention specification be
standardized?
john mcnally
On Tue, 2002-08-20 at 21:58, Martin Cooper wrote:
> >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 add the following to the Guidelines section of the Commons
> charter, 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 should be retained. If a component does not specify its coding style,
> the Sun Coding Convention guidelines are assumed.
> ---------------
>
> (Acknowledgements to Morgan for most of this wording.)
>
> This has my +1.
>
> --
> Martin Cooper
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>