cvs commit: apache RULES.CVS

1996-03-18 Thread Ben Laurie
ben 96/03/18 02:28:23

  Added:   . RULES.CVS
  Log:
  First attempt at a "rules" file for CVS. Note that I didn't make these rules
  up, I'm just writing down what I see as the consensus.


Re: cvs commit: apache RULES.CVS

1996-03-18 Thread Paul Richards
In reply to Ben Laurie who said
> 
> ben 96/03/18 02:28:23
> 
>   Added:   . RULES.CVS
>   Log:
>   First attempt at a "rules" file for CVS. Note that I didn't make these rules
>   up, I'm just writing down what I see as the consensus.

Looks like a reasonable start. I guess rule 4 is down to me :-)

Only thing is, do we really want it in that particular location? Maybe
we should have a docs directory under apache that holds all these
files.

Some other things I'd like to see would be a style guide and a "how to
send us a patch" guide.

On the style guide issue, I started to clean up some warnings yesterday
and the code style varies *A LOT* across different files. This makes it
very hard to see quickly what is happening and in some cases the coding
style is just simply bizarre by most common standards (everyone has
their personal taste I guess). For a group project I think some basic
coding standards would be a good idea.

I've always been a fan of the Berkeley style, I can dig up their
style guide if people think this is a good idea. I'll even volunteer
to clean up the current sources once we agree on a guide.

-- 
  Paul Richards. Originative Solutions Ltd.  (Netcraft Ltd. contractor)
  Elsevier Science TIS online journal project.
  Email: [EMAIL PROTECTED]
  Phone: 0370 462071 (Mobile), +44 (0)1865 843155


Re: cvs commit: apache RULES.CVS

1996-03-18 Thread Ben Laurie
Ermmm ... wasn't it you who said not to have discussions on apache-cvs a while
back?

Anyway...

> 
> In reply to Ben Laurie who said
> > 
> > ben 96/03/18 02:28:23
> > 
> >   Added:   . RULES.CVS
> >   Log:
> >   First attempt at a "rules" file for CVS. Note that I didn't make these 
> > rules
> >   up, I'm just writing down what I see as the consensus.
> 
> Looks like a reasonable start. I guess rule 4 is down to me :-)
> 
> Only thing is, do we really want it in that particular location? Maybe
> we should have a docs directory under apache that holds all these
> files.

Perhaps.

> 
> Some other things I'd like to see would be a style guide and a "how to
> send us a patch" guide.
> 
> On the style guide issue, I started to clean up some warnings yesterday
> and the code style varies *A LOT* across different files. This makes it
> very hard to see quickly what is happening and in some cases the coding
> style is just simply bizarre by most common standards (everyone has
> their personal taste I guess). For a group project I think some basic
> coding standards would be a good idea.

I'd agree, except that almost noone likes the style I prefer.

> 
> I've always been a fan of the Berkeley style, I can dig up their
> style guide if people think this is a good idea. I'll even volunteer
> to clean up the current sources once we agree on a guide.

One thing I cannot bear is any style where the opening "{" doesn't align
(vertically) with the closing "}". Where does Bark-Lee stand on this?

Also, I'm a fan of Hungarian (as anyone who has read the Apache-SSL source will
have guessed) - I'd like to see that used.

If we do this, I insist on clear instructions on how to make Emacs do it ;-)

But, lets start this thread again on the RIGHT list!

Cheers,

Ben.

> 
> -- 
>   Paul Richards. Originative Solutions Ltd.  (Netcraft Ltd. contractor)
>   Elsevier Science TIS online journal project.
>   Email: [EMAIL PROTECTED]
>   Phone: 0370 462071 (Mobile), +44 (0)1865 843155

-- 
Ben Laurie  Phone: +44 (181) 994 6435
Freelance Consultant andFax:   +44 (181) 994 6472
Technical Director  Email: [EMAIL PROTECTED]
A.L. Digital Ltd,   URL: http://www.algroup.co.uk
London, England.