Django's Code of Conduct Working Group Details Internal Processes and Governance

Code of Conduct Update

In early 2026, Django's Code of Conduct Working Group (CoCWG) officially adopted Contributor Covenant 3.0 as the project's new Code of Conduct. This change was a significant update to the community's guidelines, replacing previous versions with a standardized and widely recognized framework for contributor behavior.

Working Group Structure and Membership

The CoCWG is established by the Django Software Foundation (DSF) board and maintains a small, diverse membership. Members are recruited for diversity in geography, background, and lived experience, rather than just availability. Membership is volunteer-based and term-limited, with annual terms introduced in February 2026. A board liaison, specifically the DSF board's president, always holds a seat on the working group, ensuring direct communication and oversight.

Decision-Making and Board Interaction

The CoCWG operates largely independently, making day-to-day decisions without direct board approval. However, the working group must consult the DSF board for three specific actions: spending money, implementing drastic punitive measures, or altering the Code of Conduct text itself. Internally, decisions are first sought by consensus. If consensus is not reached, a two-thirds majority vote among members without conflicts of interest can decide. Unresolved issues are escalated to the board.

Inter-Group Collaboration

A second entity, the Online Community Working Group, handles routine moderation of Django's daily spaces. This group interacts with the CoCWG primarily when issues escalate, such as formal reports, violations spanning multiple spaces, or problems neither group can resolve independently. Each working group appoints a liaison to the other to facilitate communication and coordination. If the two groups cannot agree on a joint handling, either chair can refer the matter to the board.

Process for Code of Conduct Changes

Before any modifications were made to the Code of Conduct text, the working group established a formal process for proposing changes. This process was initiated with Issue #69 on January 13, 2026, which requested a method for proposing updates. PR #70 addressed this by adding an `updates.md` file and a structured issue template for proposals, standardizing how future changes to the Code of Conduct would be managed.