New Deputy Handbook page outlining a deputy review procedure

A few months ago, the Global Community Team received a formal complaint about the behavior of a community team deputy. This was a dismaying first, and required a new response procedure. The deputy in this case has been informed that an investigation is underway, and has been asked to refrain from actively participating as a deputy in this program until the review panel has reached a decision and informed all parties. An incident report will be published in the next week or so, with information about the resolution of that complaint. 

In the meantime, I’ve documented the procedure in a new Deputy Handbook page, with some clear information about what kind of behavior might result in someone being asked to step away from the community deputy role.

If you enjoy creating and reviewing procedures, please feel free to suggest ways to improve the current practice. If you would simply like to know what kind of behavior might result in a contributor being asked to stop volunteering as a deputy, I’ll save you a click and list the reasons below. I hope the list is straightforward, and doesn’t include any surprises. This should line up with the content of the agreement that all deputies are asked to sign before taking on the role.

Reasons a contributor might be asked to step away from their role as a deputy:

  1. Malfeasance, which may include attempted or actual fraud, or other intentional action that injures or seeks to injure an individual or group, while carrying out the responsibilities of a deputy. 
  2. Failure to meet community team expectations for a deputy, even after the deputy has been asked to change a behavior. “Deal-breaker” behavior includes:
    • Anything that does not match the expectations on the Representing WordPress handbook page.
    • Communicating with contributors (including community organizers, speakers, sponsors, volunteers) and fellow community team members in a demeaning, disrespectful, or deceptive way.
    • Breaking confidentiality of the community team email inbox, incident investigation and resolution process, or other sensitive/personally identifiable information accessed while performing the duties of a deputy.
    • Recommending that organizers or contributors work in a way that intentionally defrauds the community team or undermines community team goals.

As you can see, there are expectations for deputies that go beyond the expectations for local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on will help you find options in your area. and WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. organizers. This is because the community team deputy role requires increased trust due to its particular responsibilities and access to private information. Deputies are frequently asked to guide other contributors in their work, and therefore are expected to communicate and behave in a respectful, collaborative, and genuine way, so they can effectively work with community members and other deputies.

If you think anything in this list is confusing or surprising, or you have any suggestions for ways to improve the response procedure for cases like this, please share your feedback in a comment on this post.