Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGRH7HrDsvXhtEWs8bU-c3WvWMLCh+vu3y=0GidCBHijXR2ORQ@mail.gmail.com>
References: 
 <CAGRH7HrDsvXhtEWs8bU-c3WvWMLCh+vu3y=0GidCBHijXR2ORQ@mail.gmail.com>
Date: Thu, 23 Aug 2012 11:57:27 +0100
Message-ID: 
 <CAOGo0VY0TPPf3hRTU8khFyHCnBg0Q8O0YEsT8thAsS12xittyg@mail.gmail.com>
Subject: Re: [math] Formatting
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 23 August 2012 11:39, S=E9bastien Brisard <sebastien.brisard@m4x.org> wr=
ote:
> Hi,
> in MATH-851, a discussion about code- and comments-formatting as yet
> again taken place. It is true we are a bit fuzzy on this side. I
> propose to start writing something up in the developer's guide. This
> will be a start, and every one of you could then comment on these
> guidelines.
> The idea is to gather the compulsory rules, as well as some optional
> rules, which should then be complemented by the rationale for these
> optional rules.
>
> What do you think ?

Probably easiest to use the Wiki for this, at least initially.

If there are compulsory rules - e.g. no tabs - a reason should be
given, for example:
Tab settings vary. This causes alignment issues, so tabs are banned.

Generally it's easier to understand and follow rules if their purpose
is made explicit.

> S=E9bastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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