This section shines a light on best practises and processes to be carried out before and during the event. We recommend certain follow-up activities and measures for the time after the event is over and the CoC is no longer in force.

Drafting and implementation process

For large events such as a national or international conference/ meeting in which numerous people are expected to participate, it is a good practice to delineate the process through which:

  • the people drafting the CoC were selected.
  • members of the Incident Response team/ Trust and Safety team were selected.
  • the CoC was adopted.

Workflow for drafting the code of conduct

This is a workflow we recommend for drafting the CoC of a large event and implementing it. You may adopt as it is or modify it to suit your event and/ or community:

  • The team/ committee that chalks out the CoC meets (online or in person) to develop the draft. The CoC also includes the procedure to raise a complaint and the mechanism(s) through which the complaint will be addressed.
  • The draft is then circulated among the event organisers, the teams handling logistics, security and selection of sessions, speakers and participants, and any other stakeholders. At this stage, it is possible to determine if all provisions of the CoC can be met in terms of the monetary resources, time and humanpower they require.
  • After the CoC team has addressed all comments and suggestions from every group, the CoC is published on the relevant wiki for review by the community. The call for review and comments is announced on Village Pumps, mailing lists, on-wiki noticeboards, and any other avenue the CoC team and the event organisers deem fit.
  • The community is allotted a reasonable amount of time to respond to the call, ask their queries and make other interventions. Regardless of the process, the CoC should never be thrust on the participants on the day of the event or at extremely short notice. They should have adequate time to read and peruse the CoC.

The CoC should be binding on all participants, speakers, facilitators, organisers and volunteers. The registration form or similar process implemented to gain entry into the event venue should include a checkbox that reads, "By registering for this event, you agree to abide by the Code of Conduct". This notice should be followed by a link to the CoC and the complaint redressal process.

Dissemination of the code of conduct

It is a good practice to also distribute copies of the CoC with the conference kit and make an announcement at the start of the day that the event is governed by a CoC under which violations may be reported. For a large event, posters may be put up in busy places -- such as the entrance to the venue, registration desk, cafetaria and washrooms -- about the CoC and how to access help or raise a complaint in case of a violation.

Review and revision of a code of conduct

Like everything else in Wikimedia communities, a CoC is open to review and revision. Community review can happen before a CoC is adopted or when the need arises to revisit specific provisions (or lack thereof) in it. This can be done via the RfC (Request for Comments) process.

Apart from adhering to Wikimedian values of transparency, community collaboration, and building consensus, the review process gives the participants a sense of ownership of the rules they are supposed to abide by.

Evaluating a code of conduct

A good resource to learn about how to evaluate a CoC is this document by Geek Feminism: Among other things, it states that, "Important elements of an effective code of conduct include:

  • Specific descriptions of common but unacceptable behavior (sexist jokes, etc.)
  • Reporting instructions with contact information
  • Information about how it may be enforced
  • A clear demarcation between unacceptable behaviour (which may be reported per the reporting instructions and may have severe consequences for the perpetrator) and community guidelines such as general disagreement resolution."
next: Process for redressal of complaints