Re: Policy on pkgs with same filename and QA rant (was: Re: Mercury compiler (policy, anybody)?)

[Mark Eichin <eichin@cygnus.com>]

> all parties).  And consensus is the best way to accomplish said
> excellence (I cite the Internet STD documents and Linux kernel

There's a difference between "consensus" and "rough consensus"; the
IETF credo is (well, was) "rough consensus and running code"...

Sometimes (*particularly* in cases like the mc vs. mc example) if
there is no "technical" right answer, and the only way to do any good
is for someone to simply assert an answer out of *leadership* and then
we can move on...  I agree that we should *strive* for most excellent
technical answers -- but we should recognize where that's a waste of
time...