John Plocher wrote: > Garrett D'Amore wrote: >> This should be in a document tree that is referenced by this 20Q. > > Like the ARC Policy and Best Practices repository? > > Maybe an explicit reference would be good: "Please provide detailed > rationale for any ARC Policies and/or BPs you don't adhere to". > > > -John
So where are all the ARC policies and BP clearly spelled out, such that someone could evaluate their project's compliance? Telling someone to read the last 17 years of ARC cases before submitting a case is not very practical, and does nothing to simplify ARC processes. Attempting to use the Socratic method to tease out potential areas of non-compliance via the 20q obviously doesn't work very well either. If the ARC(s) were to modify their procedures such that all policies had to be enumerated in a single living & versioned document, project teams would be a lot better off. This single document would reference the relevant case materials as background material, but most project teams really don't need to know the details about why something is a rule, just that it is. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird."
