Also, if a project was deciding on it's own code of conduct, that's one thing. But when you have people creating twitter hate mobs that threaten to contact your employer and get your fired, or get you blacklisted from events if you don't adopt their CoC, it's not really the project owner's wishes. The people trying to force adoption of certain CoC frequently don't even participate in the project who's owner they're harrassing.
We are all adults. We accept anyone's contributions. If you are feeling harrassed speak up by yourself. We do not censor, we don't stop any discussions. Nothing else matters.
This may be a perfectly reasonable caveat, as the given example that follows seems to be, or not, because it doesn't really say much more detail than that. But it's fairly certain it means that the CoC is not strictly limited to Mozilla resources and functions and how you behave in them; i.e., it isn't just project-wide, and you might run afoul of it other places. I know it certainly gives me pause to consider, and I've been a Mozilla community member for almost 15 years.
I, personally, would feel much more welcomed by those which adopt non-violent communication. RMS' recent proposal is one such example.
Ah, so you are OK with their original CoC, right?
As an American who believes in the separation of church and state, I definitely understand and sympathize with the instinct that, although religious laws often provide good moral guidance for secular codes of conduct, the two serve distinct purposes. You don't have to reject the ten commandments to recognize why we need more graularity and detail in actual laws regarding murder.
As a developer, I recognize that there are concrete and specific ways in which documents like The Rule fail to meet the pragmatic needs of a code of conduct, including:
1. clearly delineating acceptable from unacceptable behavior
2. establishing a reporting mechanism
3. codifying specific consequences for doing things that were clearly delineated as unacceptable.
A perhaps important thing to realize about monkish orders is that they were intrinsically self-selecting; you didn't need to worry about the "spirit" vs. the "letter" of the law. Monks did not need to worry about people misunderstanding ambiguously stated laws (e.g. "love thy neighbor"). The process of joining a monk-hood or a a religion includes an indoctrination/inculcation/instruction into the "spirit" of the law. Sending a pull or posting on a message list is not even remotely similar.
I.e., if you want to extend the development community beyond a small a close-knit group who understands each other, then you need something closer to laws than to religious commandments.
But of course, the development community for SQLite has always been, and likely will continue to be, a close-knit group who understands each other. Which means that the requirements for a "true" code of conduct (the benefits of which have yet to be proven) don't really apply here.