Tracy, at least to me, code review write ups of that sort
sound like something that should preferably be published on
openacs.org, rather than just sent to one or two members of the OCT.
IMO, the more solid technical review that gets done in the
open, the better off OpenACS will be.
If there are, say, proprietary client-specific details embedded in the
report, then that's good reason to keep it private until you can find
the time to do a 2nd draft. But if it's fear of stepping on other
developers' toes (aka, politics), well, I think some toe bruising is a
cost worth bearing.
