1328: Maintenance For Code Review Standards

carlo.c*******@gmai***** (Google Code) (Is this you? Claim this profile.)
Oct. 5, 2009 
board.org/


What version are you running?
1.1 Alpha 1

What's the URL of the page this enhancement relates to, if any?


Describe the enhancement and the motivation for it.

Code Review Standards Maintenance. For example I do a code review and it
violated rule, I can simply point to that ruleu using a select box or
something. 

For example I create a rule standard 1. Avoid using this....
                                     2. Always use apostorhphe....

I can point my code reviews for example, this review violates rule 1
this review violates rule 2

What operating system are you using? What browser?


Please provide any additional information below.
david
#1 david 
I've been thinking about this, and I don't think there's any way we can do it which
will scale to the standards used in a serious, large software project. Coding style
documents are typically dozens of pages of rules, and are more for initial reference
when learning a new codebase than continued development.

Saying "this code violates rule 1" isn't a helpful way to review people's code
because then they have to go look up "rule 1."
  • +WontFix