[VOTE] Coding standards

[Jordi Salvat i Alabart <js...@atg.com>]

> 1. Switch from tabs to spaces for indentation.
> [The overwhelming consensus is for spaces, but I am retaining this here for
> one last round of objections - but remember this is consensus voting where
> the majority rule]
> 
>     Scott Eade: +1
Jordi Salvat: +1

> 2. Adopt Sun's coding standards
> (http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html)
> 
>     Scott Eade: +1
Jordi Salvat: +1

> 3. Adopt the additional coding standards from the Turbine projects
> (http://jakarta.apache.org/turbine/common/code-standards.html) (only vote +1
> for this if you are also voting +1 for spaces)
> 
>     Scott Eade: +1
Jordi Salvat: +1

> 4. Whatever standard is adopted, the best approach to making the switch is
> to reformat the code and commit with an appropriate comment (e.g.
> "Reformatting code") separately (and preferably prior) to making other
> changes (just reformatting with no subsequent change will also be
> acceptable).
> 
>     Scott Eade: +1
Jordi Salvat: +1



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

AW: [VOTE] Coding standards

[Wolfram Rittmeyer <w....@proplant.de>]

And for this one also +1 for all four votes,

Wolfram


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: [VOTE] Coding standards

[Drew Gulino <dr...@yahoo.com>]

> > 1. Switch from tabs to spaces for indentation.
> > [The overwhelming consensus is for spaces, but I
> am retaining this here for
> > one last round of objections - but remember this
> is consensus voting where
> > the majority rule]
Vote +1

> > 2. Adopt Sun's coding standards
> >
>
(http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html)
Vote +1

> > 3. Adopt the additional coding standards from the
> Turbine projects
> >
>
(http://jakarta.apache.org/turbine/common/code-standards.html)
> (only vote +1
> > for this if you are also voting +1 for spaces)
Vote +1

> > 4. Whatever standard is adopted, the best approach
> to making the switch is
> > to reformat the code and commit with an
> appropriate comment (e.g.
> > "Reformatting code") separately (and preferably
> prior) to making other
> > changes (just reformatting with no subsequent
> change will also be
> > acceptable).
Vote +1


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>