A large chunk of frequent contributors are paid by companies to heave features/drivers at the kernel with no regard to doing it the right way. To them it's abou

A large chunk of frequent contributors are paid by companies to heave features/drivers at the kernel with no regard to doing it the right way. To them it's about landing code ASAP. Linus is already working in the win/win quadrant by default by merging these things all in the name of making the kernel better. Occasionally a frequent contributor who has gained trust will start to merge trash in the name of meeting deadlines. This is usually when linus loses his shit at the people responsible. This has nothing to do with a silly quadrant of being competitive/neutral/anything towards the collaboration itself. Linus is still looking for a win/win, but he's requiring people to fix their shit. That quadrant is irrelevant about Linus's behavior because he's always collaborating. What you need is a quadrant describing how feedback is delivered to subordinates.