William James writes: > > If someone doesn't actually want to see his work reviewed, then I > > think it'd probably be better to find a gate that doesn't care about > > peer reviews. Of the ones to choose, ON is historically probably > > among the most picky. > > Does this necessarily include rigidity? I mean Roland has given a fair > rationale why this kind of file should be in the CVS and then even > offered a compromise which includes a removal of the file if it is no > longer required. I find it a bit unfair that this is being ignored.
Frankly, the rigidity I see isn't all on the side of the reviewers. In fact, I've seen folks bending over backwards to accomodate this project, including agreeing to the (in my opinion) incorrect inclusion of SUNWastdev in SUNWCdev. That one's a much larger concession, as it will end up littering _customer_ systems for no useful reason that I can discern. The point here isn't to trade favors or make people happy. It's to arrive at solutions that work well and don't end up making a mess in the future. It's still quite unclear to at least some of the folks looking at this why a file that can be regenerated at will via "diff -r" and that plays no part in either the build process itself or in documenting the source is something that's worthwhile to store in every copy of the repository. And, no, pointing to other projects that may have integrated useless bits in the past doesn't answer the question. We don't actually have an integration rule that allows mistakes if enough others have made similar ones. Instead, we file bugs. Perhaps I'm missing some vital component here, but being inflexible in order to keep something you don't actually need does not seem too helpful. I realize that this file is essentially a very tiny issue, and that it's probably entirely worthless to try to discuss it at all, but I do think that the broader issue of having reviews that are based on the technical issues rather than granting project teams private playgrounds in public spaces is important. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
