Re: A different approach to a conflict resolution document
To get the discussion rolling even faster, given the broad
categories of the kinds of situations where conflict resolution may
be required, it would be nice to have an idea what pushes peoples
buttons (I know what pushes mine, but I would like to hear other
A recent button was fast reports about new versions of
packages (not a very good example, since the rapid consensus on IRC
seemed to be that one should accept that as part of the cost of doing
business as a developer).
A first place to look at is the list of conflicts submitted to
the tech ctte. Or the last few flame wars ;-).
I guess we should realize that this document is not there to
merely address disagreements -- it is the knock down-drag-around kind
of conflict we need to look at.
... I want FORTY-TWO TRYNEL FLOATATION SYSTEMS installed within SIX
AND A HALF HOURS!!!
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C