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.


  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

WordCamp Europe 2018 – Community Team Plans

Yesterday I was reminded by a nice poem that WordCamp Europe 2018 is 50 days away. Woot woot!

The day has yet to come,
but we can already hit the drum.
You may or may not know,
that today marks 50 days until the show.
So, it’s time to plan your stay,
hey, you don’t want to miss the day.
Book the hotels, get your flights,
and get ready to see Belgrade’s lights.

— WordCamp Europe (@WCEurope) 25 aprile 2018


WordCamp Europe and WordCamp US are what we consider flagship events and are always a great opportunity for teams to get together, contribute and onboard more people. There are going to be a whole lot of us present and we should take advantage of that and maximize our time together.

This year, in addition to the Contributor Day, there is a Community Room, which sounds like an amazing opportunity to continue conversations or start new ones in a nice environment. Here is the info we have from the WCEU team:


The Community Room will be open all day on both days of the main conference. It is located just off the area where both the Get Involved table and the Happiness bar will be set up, so is the perfect place to take any longer conversations that start there over to. The room will be set up with tables and chairs as well as some more comfy seating. Any Make groups who want to continue work in this space left over from Contrib day can. If you think some paperboards or whiteboards might be useful, let us know, we can probably work something out. Note, like last year, Contrib Day is the day *prior* to the conference. So the Community Room is thought of as carry over from Contrib day as desired. It won’t be a restristed space either – someone who needs to take a work call or shoot off some emails or whatever would be welcome to hang there.


This room is not “mandatory” for any team, it’s meant to be for people who’d like to continue contributing, or who weren’t able to attend Contributor Day, or haven’t heard of Contributor Day, etc It is mostly to create bridge between conference days and Contributor Day and to generally increase awareness for contributing to the project.

As we did last year, please add in the comments ideas and suggestions for tasks we could work on together while in Belgrade and ideas for the Community Room: again, presence there is not mandatory, so there is no pressure to “staff the table”, but it is definitely a great initiative and we could think of something cool for it as well.

Deadline to comment is May 18 so we can discuss this during the next two Community chats: after that date I will summarise in a post (like the one we had last year) and we will go from there!

#wceu, #wceu-contributorday

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.


  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

Moving WordCamp Ticket Sales from PayPal to Stripe

For some time now, we have been using PayPal as the default payment gateway for WordCamp ticket sales. In addition to that, WordCamp organisers have also been able to create custom payment gateway integrations for our ticketing plugin, CampTix. While these options have generally worked for most events, there are times where neither of them are optimal solutions. One of the main issues is that PayPal only has limited currency options, which is why some communities have built local gateway integrations, but in those cases the ticket sales then need to go through a local bank account — something that isn’t always practical.

There is now an alternative — @dd32 has built a Stripe integration for CampTix. This can be used by WordCamps that request it (please email if you would like to use it instead of PayPal).

I would like us to discuss the feasibility of switching to Stripe as the default gateway while using PayPal as an optional alternative, with a view to eventually deprecating PayPal entirely and switching to Stripe as the only core gateway in use.

Some of the advantages of Stripe over PayPal are:

  • The UI is arguably simpler for purchases.
  • PayPal is entirely blocked and inaccessible in some countries.
  • Stripe offers support for way more currencies than PayPal does, which would allow more WordCamps to sell tickets in their local currency without needing to write a custom gateway integration.

Before this can be implemented, I think it would be valuable to gather some community feedback about this move to see if it is indeed an option worth pursuing. Please comment below with any feedback you have about this potential move — it would be great to know about any reasons you have for preferring one gateway over another and what impact this could have on your local WordCamp.

WordCamp Volunteer Guidelines relating to GPL

In the comments on this post a point was raised that warrants further discussion:

A person works for a marketplace that sells non-GPL WordPress products. They want to help organize or volunteer at a WordCamp.

When vetting all Volunteers for a WordCamp we use the 100% GPL vetting checklist and the GPL Primer We define Volunteers as organizers, speakers, and volunteers. We have a belief that our events should reflect the core projects beliefs and philosophies, especially with regard to the GPL. Anyone associated with WordCamps in a Volunteer role is our representative. It is important that they reflect the projects values. We look at all Volunteers and review and WordPress derivative products and ensure that they are GPL. If not, we ask them if they can change the license to GPL. If they cannot, they cannot be a Volunteer at a WordCamp.

In the Comments a comment thought was repeated:

link Personally I think I should be judged on my own software, which is all 100% GPL, rather than my choice of employer.


link I think individuals who work at such a marketplace should be able to organize, participate, get involved etc. as long as they are representing themselves and not their company.

My employers do not exist within the WordPress realm so that’s easy for me to write. It just does not come up and when I participate in support at an event, it’s just me.

But if my employer was against opensource (they’re not, I checked), I don’t want my participation to be evaluated on that basis. My involvement as an individual contributor should be an option.



link there are two key things to bear in mind here:

The current rule that requires all WordCamp organisers, speakers, sponsors and volunteers to be 100% GPL compatible, extending to the company that they work for, is one that we cannot currently make an exception for. That’s how it is at the moment and individual exceptions cannot be made right now. Which brings me to the second key point…
While I think I can safely say that we will never change the rule that individuals must be GPL compatible in their personal capacity, there is a valuable discussion to be had with regards to how we handle individuals who are personally compatible, but their employer is not. This is the case that @stephencronin explained above with his employment at Envato. As @kcristiano has stated, this is a discussion better held in a dedicated post and I think it is a discussion that we need to have. I’m not sure what the outcome would be at this stage, but we definitely need to talk about it and make a firm decision that both upholds the principles of the WordPress project and remains as inclusive as possible.

I do agree with @hlashbrooke that we should take a look and decide how to handle individuals who are personally compatible with the GPL license, but work for a Company that is not. We’ll hold this post open until April 3rd for comments. Please chime in with your thoughts.

Link to Summary



WordCamp Fundraising Research

@andreamiddleton suggested a Fundraising Working group in her post.   In short, the scope will be:

The scope of this project is to research the methods and practices of organizing teams that have been successful in their fundraising and then report back to the global community team with the results. The team may decide to try to send a survey out to WordCamp organizers, or might decide that interviews would be a more effective way to gather data. Volunteers with experience in successful WordCamp fundraising would be a big asset to this working group. We’ll be reporting which camps ran surpluses and deficits at the end of this year, so the group will be able to target their research.

I would like us to get started on this working group. I am pinging @psykro and @kdrewien as you both expressed interest in the original post. I would also like to ask anyone else that would be interested to indicate so in the comments before March 10th. We can then schedule an initial meeting to get started.

A Trello Board for the Community Team

During our first chat of February we discussed the idea of opening a Trello Board to check on our progress for projects and working groups.

The idea is not to use it for daily tasks, like vetting, emailing, etc… but more for broader tasks. These could be some of the goals we have in mind for 2018 and other ideas that will pop up in the next few months that need followup.

We are not sure this system will work for us, so we are setting a trial period of 3 months from the moment we create the board to see if someone uses it.

We have two models to look at:

As you can see the different lists have projects in it and not simply “To Do/Doing/Done” which is the default you get when you open a Trello board.


  • open a Trello organisation under the email, so it’s not linked to a specific individual
  • create two boards: “Start here” with the workflow “Community Tasks” with the actual tasks
  • after we do a summary of the 2018 goals, see which ones need project management
  • the person who will work on a specific task will start a list

As far as the “Start here” board goes, I think we can see what Design and Marketing did and adjust that to our needs. I am no project manager, so if someone here is, please point us in the right direction of an efficient Kanban board use 🙂


Please leave your feedback before Thursday, Match 8th. We can discuss this during our next chat, on March 1st and then I’ll summarise comments and move to the next step.

Thank you!

Handling Dormant Meetup Groups

With 575 meetup groups on the chapter account (and always growing!) we like to check in every so often to confirm if the groups are active. However, there are some meetup groups in the program that are inactive or dormant, and we need to figure out how we should manage them going forward.

A few weeks ago, I exported a list of current chapter meetup groups to a spreadsheet and sorted them by the date of their last event. A quick guide to this spreadsheet:

  • Groups highlighted in Red haven’t had an event in over a year.
  • Highlighted in Orange haven’t had an event in 6–12 months.
  • Highlighted in Yellow haven’t had an event in the past 3–6 months.
  • You’ll notice a column titled “Upcoming Events”, which we’ll need to investigate for each group, as it can mean they have an event listed, but don’t have a location and/or date yet.

In some inactive groups, organizers are still interested, but they are struggling with attendance and/or finding event topics. We should check if this is the case, and if we can help advise/support them in any way.

I propose the following plan:

  • Email existing organizers of dormant groups that we have contact info for (according to the Meetup Status doc).
  • Also reach out to the organizing team via message on (this will help ensure that the message reaches organizers that we don’t have email addresses for, and/or if their contact information has changed).
  • If we don’t hear back from any organizers for a particular group by 5 March 2018, we will then reach out to all the members of the group via message to ask if anyone is interested in organizing.
  • If no members of the group volunteer to organize the group by a 12 March 2018, we will remove the group from the chapter account.

Below is the email that I’ve drafted, which is based on an old annual survey email that we sent to dormant groups. Please let me know if you have any suggestions for changes and/or additions.

Continue reading

Potential addition of a new Onboarding Team

Hi Community Team!

Recently I proposed an addition of a new ‘Make WordPress Team‘, currently there’s well over 15 different teams from Core, Polyglots, Mobile and even Marketing. However I feel like there’s one team that is missing and is a huge part of what makes WordPress, WordPress. The new team would be focused around on-boarding new contributors to the WordPress project and also help in steering them where they need to go depending on how they want to get involved. Sort of like a hotel concierge service (sort of).

Now, whilst the community team does a great job at the community side of things such as WordCamps and meetup events to name a couple of things and getting people involved – this new team would reach beyond what the community team does and also cover every other team in WordPress as well. I’ve heard first hand from others (myself being one!) that getting involved with WordPress is incredibly difficult. There’s so many moving parts and all kinds of things happening that it’s very hard to make that first contribution. Even so, once you’ve made the first contribution, it’s hard to find out where to go next.

Here’s the low-down of what (I think) the team would do:

  • Liaise with other team leads on ‘good first bugs’-esque contributions for things like Core & Design.
  • Work with the training team and marketing teams for producing help guides and tutorials.
  • Quick start help with getting involved with the Plugin and Theme contributions.
  • Talk with the community team on how to get involved with WordCamps and meetups.
  • Other outreach work with the Make/Teams.

And my favourite of all points:

  • Mentorship programme with on-going support for people who might not be as confident contributing or for people who want to try their hand at all sorts of things. Giving insights into the WordPress philosophies, community and code of conduct.

So, what do I need from you guys?

Help. Please discuss this, let me know what you think and raise any points for concern or potential ideas we can include. Whilst I appreciate this isn’t strictly community related, and I’d like to ensure that this team is separate from the community as a whole – this new team will overlap in some form or anything with every other team in the community.

Also, some more food for thought, some team names!

  • Welcoming Team
  • Concierge Team (Hotel WordPress anyone?)
  • Onboarding Team

Thank you!

Community Team Chat Summary| 7 December 2017

Yesterday’s team chat (Slack logs for 8:00 UTC and 20:00 UTC chats) covered the following ground:

  1. Deputy check-in
    Things are going smoothly as we near the end of the year – only a few WordCamps left to go, so mentors are slowing down a little and the team is generally recovering from WCUS.
  2. Conclusion of micro-regional WordCamps discussion
    Nothing to really discuss here, but worth taking note of the summary to the micro-regional WordCamps discussion.
  3. Payment intermission
    There will be a payment intermission (i.e. no WordCamp or meetup payments will be made) from 23 December – 2 January
  4. do_action docs updates
    We have update the deputy docs, orientation script and organiser docs for do_action events. Deputies are encouraged to familiarise themselves with this info so they can assist with the management and support of do_action events.
  5. P2 posts needing review/feedback
    We wrapped up with some P2 posts that need deputy review and/or feedback:

Anything I missed out? Leave a comment below!