Django Code of Conduct - feedback wanted

Posted by Jacob Kaplan-Moss on April 1, 2013

When Adrian, Wilson, and I first started talking about open sourcing Django, we knew that we didn't want to just throw the code over a wall and walk away. We wanted to build a community around the code, and we wanted that community to be one we'd enjoy.

Well, we succeeded beyond anything any of us could have imagined. Today, the Django community is this amazing, vibrant, exciting, exuberant thing, spanning the globe, encompassing tens of thousands of people from all walks of life. It's a community I'm intensely proud of: open and welcoming, friendly and helpful, calm and considerate.

But, like every growing thing, we have some growing pains. As we grow past the point where it's reasonable to expect that everyone knows everyone else, our values risk dilution. If we want this community to remain one that lives up to its ideals, then we need to be explicit about what those ideas area. (After all, explicit is better than implicit!)

To that end, the Django core team and the Django Software Foundation are working on formally adopting a code of conduct. It's a statement of ideals: it's a way for us to articulate what it is we think makes our community so great. Today we're publishing a rough draft of that document. Think of it as a "beta" release: we think it works, and we like it, but we want community feedback before we adopt it formally.

So please: check out the rough draft, read the FAQ, and if you've got questions, comments, criticism, or other feedback, then let us know.

Back to Top