By rachel_norfolk on

This time last year, members of the community collaborated on a major update to the DrupalCon Code of Conduct, and it proved to be a success. Indeed, we surveyed attendees after DrupalCon Nashville and asked the following questions:

  1. “On registration, and during the event, were you made aware of the CoC and how to report violations?”
    - 73% answered “yes”
  2. “Did the existence of the CoC make you feel safer, and more empowered to fully participate at this event?”
    - 70% answered “yes”

I also said that we would review the code on an annual basis and it is now time for this year’s review period. I am, therefore, inviting proposals for changes to the code on the community project at https://www.drupal.org/project/drupalcon_coc.

As it will soon be time to commit to printing the program guide and signage for DrupalCon Seattle 2019, we will make a release of the code on the 4th February 2019. Any issues not closed by that point will rollover until DrupalCon Minneapolis 2020.

I’m looking forward to reading your proposals for how we can continue to improve our Code of Conduct!

Comments

nerdstein’s picture

nerdstein
he/him
Primary language English
Location United States
commented

I really like the format and simplicity of the AWS Code of Conduct. It would be worth exploring that for relevance, as they describe various types of events.

j. ayen green’s picture

j. ayen green commented

The message delivered by the CoC is a good thing. The implication being that the desired conduct, these Drupal Behaviors, is not the default to some of our community of adult professionals is a sad thing. 

mrgoodfellow’s picture

mrgoodfellow commented

I'm in the opinion that something simple can be most effective.  Take for example:  The Golden Rule.

headstartcms’s picture

headstartcms
Primary language English
commented

Organized and review is one of good ways.