Meetup Application Vetting Sprint – 26 & 27 September

In order to get through the large backlog of meetup applications that are currently in need of vetting, we are going to be joining together in two 1-hour vetting sprints next week!

What is a vetting sprint?

A vetting sprint for meetup applications is a 1 hour session where all available deputies meet together in the #community-team channel in the WordPress Slack group. Over the course of the hour, we will all work on vetting meetup applications and use the Slack channel as a central place to discuss what we’re working on and support each other.

Who can take part?

Any deputies who have access to the Meetup Tracker can take part. That means people who have completed the deputy training, signed the agreement and been given access to the tracker (details about the tracker here).

If you are a deputy who has been active in the last 6 months, then you would have been added to the tracker already, but if you don’t have access and still want to take part then please comment here and we can give you access.

When is this happening?

We have two sprints planned for next week, so we can accommodate as many time zones as possible. The two times are:

These times have been added to the Deputy Calendar for easy reference.

How does it work?

As explained above, we will meet in the #community-team channel on Slack at the times listed and dive into vetting meetup applications. Here are some handy links that you will need on the day:

Community Team Chat | Thursday, May 3rd 2018

Hey Team!

Our bi-monthly Community Team chat is happening this Thursday, May 3rd 2018. Meeting times are 11:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

Agenda

  1. Deputy check-in:
    What have you been doing and how is it going?
  2. P2 posts needing feedback/discussion:
  3. New posts on P2 (no feedback needed, but reading appreciated to be up-to-date!)

Please add any additional items to this agenda by commenting on this post as needed.

#meeting #agenda

Community Team Chat Agenda | Thursday, 5 April 2018

Hey Team!

Our bi-monthly Community Team chat is happening this Thursday, 5 April 2018. Meeting times are 11:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

Agenda

  1. Deputy check-in:
    What have you been doing and how is it going?
  2. WordPress 15th Anniversary Plans:
    We want to support the community in celebrating the 15th anniversary of WordPress, so we have some resources to assist with that – see the announcement post and handbook page. Let’s use this time in the meeting to clarify any questions so all of us are on the same page when community members ask about it.
  3. P2 posts needing review/feedback:

Please add any additional items to this agenda by commenting on this post as needed.

#meeting #agenda

Community Team Chat | Thursday, 1 March 2018

Hey Team!

Our bi-monthly Community Team chat is happening this Thursday, 1 March 2018. Meeting times are 08:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

This site has enjoyed a lot of activity in the last few weeks, yay! There’s a lot we *could* talk about, but a few topics that folks have raised specifically for discussion, so this agenda will focus on those. As always, if you’d like to suggest a topic, please do so in the comments below!

Agenda

  1. Deputy check-in:
    What have you been doing and how is it going?
  2. Calls for volunteers:
  3. Proposals for discussion:
  4. In Case You Missed It (ICYMI):

Please add any additional items to this agenda by commenting on this post as needed.

#meeting #agenda

Community Team Chat | Thursday, 15 February 2018

Hey Team!

Our bi-monthly Community Team chat is happening this Thursday, 15 February 2018. Meeting times are 08:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

Agenda

  1. Deputy check-in:
    What have you been doing and how is it going?
  2. How should we handle secure access for inactive deputies?
    A number of deputies are unable to commit time this year, so we need to talk about the best way to handle their secure access while they are inactive (Help Scout,etc.)
  3. How should we handle dormant meetup groups?
    Many meetup groups in the programme are inactive or dormant – we need to work out ho we should manage them going forward.
  4. How should we add content to meetup pages in the new design?
    Whenever we create a new meetup group, we add some default content (code of conduct, etc.) – the new Meetup design makes those pages hard to find, so what’s the best way of adding the content now?
  5. P2 posts needing review/feedback:

Please add any additional items to this agenda by commenting on this post as needed.

#meeting #agenda

Community Team Chat Agenda | Thursday, 1 February 2018

Hey Team!

Our bi-monthly Community Team chat is happening this Thursday, 1 February 2018. Meeting times are 08:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

Agenda

  1. Deputy check-in:
    What have you been doing and how is it going?
  2. Email addresses and support queues for working groups:
    This is important to take note of and make suggestions where necessary.
  3. P2 posts needing review/feedback:

Please add any additional items to this agenda by commenting on this post as needed.

#meeting #agenda

Community Team Chat Agenda | Thursday, 18 January 2018

Hey Team!

Welcome to the new year – we’re very excited to kick things off with our first meeting of 2018 this week!

Our bi-monthly Community Team chat is happening this Thursday, 18 January 2018. Meeting times are 08:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

Agenda

  1. Deputy check-in:
    What have you been doing and how is it going?
  2. 2018 goals for the global community team:
    We have a post to gather feedback for our goals this year, so let’s start putting some ideas together.
  3. P2 posts needing review/feedback:

Please add any additional items to this agenda by commenting on this post as needed.

#meeting #agenda

Community Team Chat Agenda | 17 August 2017

Hey Team!

Our bi-monthly Community Team chat is happening this Thursday, 17 August. Meeting times are 08:00 UTC and 20:00 UTC in #community-team on Slack – we use the same agenda for both meetings in order to include all time zones.

Agenda

1. Deputy check-in – What have you been working on? Any blockers? Anything that you need help with?
2. Welcome pack for new contributorsWe’re putting together a welcome pack for new Community contributors. Thoughts need to go on the post, but this would be a good time to throw some ideas around in real-time.
3. P2 posts – Some P2 posts to highlight:

If you have any other items to add to the agenda, please post them in the comments below!

#meetings #agenda

Community Team Decision Making Process

In the past the members of the Community Team had some informal discussions about the decision making process: the conversation is very broad and we haven’t tackled it in a structured way up until now.

Since April, the Community team switched from having a single monthly chat that didn’t always had an agenda, to a bi-monthly chat, held at 08:00 UTC and 20:00 UTC to take into account different timezone, with an agenda that covers topics that might come up in our channels and highlights the latest from our blog. Attendance is good, people are engaged in the discussions and in general it seems that so far this has been a welcome change in our workflow.

It also helped us approaching broader subjects, about the Community team itself and its organisation.

One question that resurfaces every now and then is: how do we come to decisions? How do we wrap up all the discussions that float around us and come to conclusions? From comments in our Slack channels or P2 posts to issues that might be brought up to our support email, there is a lot going on in the Community team!

This is a broad conversation that touches on different subjects. The following are only a few:

  1. Media: the different media we use to communicate have different purposes, the Slack channels are for bouncing off ideas and replying to direct questions, but when we need to agree upon something we direct the person that has raised the issue to post in our P2 to gather feedback. Sometimes delicate issues are not brought in public but are dealt via email between the interested parties and then made public when a decision is made.
  2. Who: some issues are easily solved, everyone says what they think, either via a poll or comments, there are no major roadblocks (usually financial or technical), the majority of the feedback is positive so we move on. This is what happened when we decided to change the chat model. Some issues though require a more structured approach, especially if the outcome has a great impact on the whole WordPress community, not only the Community Team. Who is involved in this kind of decisions?
  3. How: after we identify the who, how those final deciders actually make the decisions they make? What processes and tools and tools can we use?
  4. Tracking: we use our P2 to gather feedback, how do we track open issues? Let’s say we come up with a workflow from now on, how do we deal with the threads that were opened in the past and never reached a conclusion?

The above items are just a few and they are mostly related to a practical workflow that defines roles, capabilities, procedures to gather feedback and come to decisions. But what about the emotional side of things? Who is taking the heat for unpopular decisions? How are they seen in the Community?

So, lots of food for thought!

Let’s set ourselves a goal of spending about two weeks on this discussion, closing it on August 3, in time for our next chat. After that I’ll gather all the comments and we’ll go from there to determine our next steps.

Thank you!

#community-team

Community Team Chat Agenda | 22 June 2017

As discussed here we have moved last week’s team chat to this week and will be holding it at 8:00 and 20:00 UTC on Thursday, 22 June 2017 in #community-team on Slack.

Here are a few agenda items that we should discuss – please add more in the comments below and we can add them in:

Community Summit recap
While we are awaiting the publishing of the notes from the Community Summit discussions, we can give a quick recap of what we spoke about to give some initial info and context.

WCEU Contributor Day recap
A lot was achieved at the WordCamp Europe Contributor Day, so I think it’s worth sharing some of the results.

Orientation script privacy
As per this post there is a bit of discussion around making the meetup & WordCamp orientation scripts public instead of private (as they are currently). Let’s chat about this and then loop back to the post to make a decision.

A few P2 posts worth highlighting