[ros-dev] Re: Vote: code auditing

art yerkes ayerkes at speakeasy.net
Fri Feb 24 04:22:13 CET 2006


On Thu, 23 Feb 2006 21:35:06 -0500
Brandon Turner <turnerb7 at msu.edu> wrote:

> " B - Sections of ReactOS which require auditing are 'locked', that being 
> that the source is fully available to download and build, but no 
> development work should be undertaken until the said code has passed the 
> audit. The lock will be removed only when that section of code has been 
> audited."
> 
> I have asked 3-4 times but still havent got an answer as far as I can tell.  Does the definition of "audit" in the pharse mean the code needs to be looked through and documented and bad code be marked.  Or does it mean all that and the marked code needs to be rewritten for it to be considered "audited".
> 
> Brandon
> 
> P.S. If the formatting is messed up in this email, im sorry.

For my part, I vote for marked.  We can decide whether some specific file
needs to remain locked one at a time and branch as necessary.
-- 
Discordant is the murmur at such treading down of lovely things while
god's most lordly gift to man is decency of mind.  Call that man only
blest who has in sweet tranquility brought his life to close.
If only I could act as such, my hope is good.
-- Aeschylus' Agamemnon (translated by H. W. Smyth)


More information about the Ros-dev mailing list