One would expect that the code in Open Source projects is constantly inspected by the users of it
For my money, effective code review is done by the programmer(s) with other programmers. This way, you get the effect of new eyes saying "why did you do it this way?", to which the answer is either "because..." or "beats me..." (either is goodness :-) ).
has anyone tried to do a systematic code review on an OS project? Did it work? Do you think it can work?
If it's done to mark off an item on a check list, NO. If it's done to make the code better (see above), definitely (at least in my experience).

In reply to Re: Code Inspections in Open Source projects by proceng
in thread Code Inspections in Open Source projects by zby

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.