However, it's sorta irrelevant here: we're not expecting this to really change much of anything, and we don't think the community needs improving. Like the FAQ says, "we know that the Django community is open, friendly, and welcoming. We want to make sure everyone else knows it too." The goal here is to articulate and write down the standards that we already basically follow but have been (until now) unwritten.
In fact, if you're worried about having the book thrown at you, you should be happy about this change. Before today, if I thought you were being a jerk, I could throw you off IRC or the mailing list or whatever and that was that. I was, until a few hours ago, essentially sole arbiter of standards in the Django community, and those standards were ones that basically lived in my head until earlier this year.
Now, those standards are written down, and there's a process and some oversight to make sure I don't unilaterally decide someone's worth hitting with the ban-hammer.
So really, if you're honestly concerned about being people ousted for violated community policies, this sort of documentation and process should make you feel more comfortable, not less. We're replacing a BDFL-ship with open documentation, a committee, and organizational oversight.