![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
> On Monday, May 24, 2004, at 11:01 AM, Mark Allman wrote: > > I'm interested in hearing your thoughts on area review teams(*) then. > > That makes things much more explicit ... i.e., "we need a reviewer from > > the security team" rather than fishing around a large general pool (as > > you note is your preference) for someone who can cover security > > documents. Does pre-sorting make for a system that is less prone to > > "gaps"? (Of course, with some alternate downsides, maybe.) > > I'm not sure. We're stretched as thin as can be on security > reviewers today, for example. Will having a more formal review > process make more security reviewers available? Probably not. I was trying to ask about your thoughts on using smaller teams (i.e., not one large pool) as a way to manage the process with finer granularity and hence avoiding the "gaps" you noted. Clearly, there are resource issues no matter which way you go. You thoughts on those are useful (as always), thanks! allman
Attachment:
pgpiC5cCh93uM.pgp
Description: PGP signature