PyCon Pittsburgh. April 15-23, 2020.

Code of Conduct Enforcement Procedure

This document summarizes the procedures the PyCon staff uses to enforce the Code of Conduct.

Summary of processes

When the work group receives a report of a possible Code of Conduct violation, it will:

  1. Acknowledge the receipt of the report.
  2. Evaluate conflicts of interest.
  3. Call a meeting of Code of Conduct responders who do not have a conflict of interest.
  4. Evaluate the reported incident.
  5. Propose a behavioral modification plan.
  6. Propose consequences for the reported behavior.
  7. Vote on behavioral modification plan and consequences for the reported person.
  8. Contact online community administrators/moderators to approve the behavioral modification plan and consequences.
  9. Follow up with the reported person.
  10. Decide further responses.
  11. Follow up with the reporter.

Acknowledge the report

Reporters should receive an emailed acknowledgment of the receipt of their report within 24 hours.

Conflict of interest policy

Examples of conflicts of interest include:

Committee members do not need to state why they have a conflict of interest, only that one exists. Other work group members should not ask why the person has a conflict of interest.

Anyone who has a conflict of interest will remove themselves from the discussion of the incident, and recuse themselves from voting on a response to the report.

Evaluating a report




Reports which involve higher risk or higher impact may face more severe consequences than reports which involve lower risk or lower impact.

Propose a behavioral modification plan

The event staff will determine a concrete behavioral modification plan that ensures the inappropriate behavior is not repeated. The event staff will also discuss what actions may need to be taken if the reported person does not agree to the behavioral modification plan.

What follows are examples of possible behavioral modification plans for incidents that occur in online spaces under the scope of this Code of Conduct. This behavioral modification list is not inclusive, and the event staff reserves the right to take any action it deems necessary.

Propose consequences

What follows are examples of possible consequences to an incident report. This consequences list is not inclusive, and the event staff reserves the right to take any action it deems necessary.

Possible private responses to an incident include:

Follow up with the reported person

The event staff will work with online community administrators/moderators to draft a response to the reported person. The email should contain:

The work group should not state who reported this incident. They should attempt to anonymize any identifying information from the report. The reported person should be discouraged from contacting the reporter to discuss the report. If they wish to apologize to the reporter, the work group can accept the apology on behalf of the reporter.

Decide further responses

If the reported person provides additional context, the event staff may need to re-evaluate the behavioral modification plan and consequences.

Follow up with the reporter

A person who makes a report should receive a follow up email stating what action was taken in response to the report. If the work group decided no response was needed, they should provide an email explaining why it was not a Code of Conduct violation. Reports that are not made in good faith (such as “reverse sexism” or “reverse racism”) may receive no response.

The follow up email should be sent no later than one week after the receipt of the report. If deliberation or follow up with the reported person takes longer than one week, the work group should send a status email to the reporter.