Index: openacs-4/packages/acs-core-docs/www/style-guide.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/style-guide.html,v diff -u -r1.10.2.4 -r1.10.2.5 --- openacs-4/packages/acs-core-docs/www/style-guide.html 22 Oct 2004 02:38:15 -0000 1.10.2.4 +++ openacs-4/packages/acs-core-docs/www/style-guide.html 1 Nov 2004 23:40:12 -0000 1.10.2.5 @@ -1,6 +1,8 @@ -OpenACS Style Guide
Alex logo
Prev Chapter�12.�Engineering Standards Next

OpenACS Style Guide

+OpenACS Style Guide

Alex logo
Prev Chapter�12.�Engineering Standards Next

OpenACS Style Guide

By Jeff Davis -

Motivation

+

Motivation

Why have coding standards for OpenACS? And if the code works why change it to adhere to some arbitrary rules?

@@ -25,7 +27,7 @@ over a long period by a lot of different people, OpenACS sometimes lacks this basic guessability and in the interest of bringing it into line we have advanced these guidelines. -

Commandments

+

Commandments

Here is a short list of the basic rules code contributed to OpenACS should follow...

  1. Follow the file naming and the package structure rules.� @@ -87,4 +89,6 @@

  2. Solicit code reviews.� Ask others to look over your code and provide feedback and do the same for others. -

Revision History

Document Revision #Action Taken, NotesWhen?By Whom?
0.1Creation12/2003Jeff Davis
($Id$)
Prev Home Next
Chapter�12.�Engineering Standards Up Release Version Numbering
docs@openacs.org
View comments on this page at openacs.org
+

Revision History

Document Revision #Action Taken, NotesWhen?By Whom?
0.1Creation12/2003Jeff Davis
($Id$)
Prev Home Next
Chapter�12.�Engineering Standards Up + CVS Guidelines +
docs@openacs.org
View comments on this page at openacs.org