Communication and Meetings

Prioritizing Public Conversations

An important part of a successful community is sharing information. To accomplish this we ask questions as publicly as possible and work as transparently as possible. Some situations do call for private conversations, but most can be addressed in the open and to the benefit of the community as a whole.

With this in mind it’s important that supporters share information: both regular updates, and if something goes wrong. 

Each time that you hold a supporter call with the organizer or team you’re supporting, please type up brief notes on where the event is and how it’s doing, and share them on the Monthly Update thread on the Make Community blog. 

share this example in the chat –

Of course, sensitive matters do come up, and sometimes teams have issues that will need to be discussed, or an organizer that isn’t meeting expectations. If you have a concern that you feel is sensitive or should be discussed privately, please send a note to to keep us informed. You can also request a time to chat if needed.

Top ↑

When and Where Conversations Regularly Happen

If you haven’t yet done so, please subscribe to updates on Make/Community blog and join the #community-team and #community-events channel in the Making WordPress Community Slack.

The Community Team’s event guidelines, tools, recommended practices, and expectations change periodically. To help keep our Supporters and other contributors informed we have some regular meetings and check-ins, as well as some best practices.

  • Monthly SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at Meetings
  • Monthly MentorEvent Supporter Event Supporter (formerly Mentor) is someone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues. Check-ins
  • Community Team Trainings
  • Slack channel messages

Monthly Slack Meetings are held the first Thursday of each month at 12:00 UTC and 21:00 UTC in the #community-team channel on Slack. You can read through them and leave feedback at any time. The times are set for community members who want to get to know one another by interacting with each other. 

If you’re mentoring an event, there are two places where we post Monthly Mentor Check-ins: in the Slack channel and on the Make/Community blog. These check-ins help us keep a record of how planning is going in a community, what it’s like to work with that particular organizer, and the overall health and atmosphere of individual communities.  

Community Team Trainings are generally held on Zoom once a month on a Thursday, and are recorded. They cover a variety of topics that help us build knowledge and skills, and work more effectively. They are sometimes used to discuss changes or new information that impacts the team.

Slack Channel Messages are notes in the appropriate Community team channels that alert the other team members that you have made a change or have a need. You might let them know you’ve made an update to a handbook, have a draft of a proposal you’d like feedback on, or have come across a question you need help answering.

Here is a current list of the Community team Slack channels:

  • Invite-only Slack channels: 
    • #community-event-supporters
    • #community-program-supporters
    • #community-program-managers
  • Public Slack channels
    • #community-events
    • #community-team

Top ↑

Invite-only Channels

The invite-only Slack channels serve two main purposes.

  • Allow teams to work without creating conversation clutter in other channels.
  • Allow teams to discuss sensitive situations while protecting community members.

Inclusiveness in these channels is maintained by having diverse individuals from across the community participate in the conversations. The members of each role hold each other accountable to be always working for the best of the WordPress community.

Last updated: