| |||||||||||
Needed: code auditorsNeeded: code auditorsPosted Feb 5, 2004 13:46 UTC (Thu) by lutchann (subscriber, #8872)Parent article: Needed: code auditors Part of the reason that nobody audits open-source code is because it is futile. For an active project, a full code audit can take as long as several release cycles, and who wants to run obsolete software? Code audits aren't a one-time event; they need to be an ongoing effort run in parallel with the development work. And, like writing documentation, it's not a fun job and nobody wants to do it.
(Log in to post comments)
fun? Posted Feb 5, 2004 15:36 UTC (Thu) by ccyoung (subscriber, #16340) [Link] Like many other thousands, I am not a kernel contributer but know C quite well. Reviewing 200-300 lines of a code a week, looking for specified classes of bugs, would certainly take less time than reading Groklaw. I think the overhead is incurred by the developers, esp at startup, answering questions on the why and how. (however it seems most of these questions should be answered with inline program doc).
|
|||||||||||