Earlier quoted context omitted.
The task of making rules like that is never ending. This concept reminds me of when the head of GM rewrote their dress code. It went from several pages down to two words: "dress appropriately". What that means actually depends on context - who are you meeting with and what kind of work is going on. She realized that manager who needed a manual to figure that out had bigger problems.
Software developers, who are intimately familiar with the idea that software needs constant attention and maintenance, seem to often balk at the idea that communities also need constant attention and maintenance. The idea that a code of conduct is "never ending" does not seem like a bad thing to me. As an example, the mozilla community participation guidelines (currently at version 3.1) are quite short and readable a…
So another area where that type of thing can happen is in union negotiations. Unions in the US started out fighting for basic decent treatment - reasonable hours and pay, safer working conditions, etc... Some years ago I was in a manufacturing plant and the break (lunch) room had a big television in it. Turns out the union had demanded the TV in their most recent contract. Someone I was speaking to berated the union "those idiots demand a TV, don't they have real concerns?" I realized the problem is that the adversarial nature had grown so bad - probably on both sides - that nothing could be had without a negotiation and putting it in writing. That goes for work from the union: "that's not my job" or worse - "you're getting written up for doing something that's someone else's job" to the management "no we're not giving you anything we don't have to by contract". Once you start writing things down and trying to nit-pick it can lead to a terrible place where nothing is easy for anyone.