Weekly Updates

Hello to all our Deputies, WordCamp organizers, Meetup wranglers, and WordPress Community builders! You were probably hard at work this weekend. Tell us what you got accomplished in our #weekly-update!

Have you run into a roadblock with the stuff you’re working on? Head over to #community-events or #community-team in Slack and ask for help!

Proposal: existing documentation to be merged into the handbooks

We some seriously amazing content in the blog that could be merged or at least linked into the handbooks.

Here is the list with the actions that I propose we take:

Proposed WordCamp Editorial Calendar

Create a new page in the WordCamp Organiser Handbook > Publicity > Website Content

Promoting Your Local WordPress Meetup

Create a new page in the Meetup Organiser Handbook > Promoting your Meetup

What makes a WordPress Meetup Great?

Create a new page in the Meetup Organiser Handbook > Building and growing a meetup > A collection of videos to inspire you

do_action Zurich 2018

Link in the Meetup Organiser Handbook > do_action: Charity Hackaton

WordCamp Design Kit Producing assets and finding a…

Merge in the WordCamp Organiser Handbook > Publicity

Collecting ideas & methods for Meetups promotion / growth

Create a new page in the Meetup Organiser Handbook > Promoting your Meetup

Summarise together with the “Promoting your local WordPress Meetup” post above

Handbook Page: WordCamp Marketing/Ticket Sales Tips

Merge in the WordCamp Organiser Handbook > Publicity

Contributor Day Room Signage

Merge in the Contributor Day Organiser Handbook

Contributor Night – An experiment in Torino, Italy

Add a page in the Contributor Day Organiser Handbook > Other Contributor Events

Also: change the name of the handbook from Contributor Day to Contributor Events

Deadline: July 22nd. If no one objects or points out different possible places to have this content, I will go on and do it 🙂

Thanks!

#documentation, #handbook

Stripe will become preferred payment gateway for WordCamps

Stripe was made available to all WordCamps last week. As a continuation, the payment layout is now changing so that the Stripe payment option will be displayed more prominently, compared to other payment gateway providers.

 

Screenshot with Stripe selected

These payment layout changes will also make discovering other payment options easier, and is a UX improvement over the select box that we currently use.

 

Screenshot when other payment options are selected

Screenshot when stripe is not available

Screenshot when only one payment option is available

This change will not affect WordCamp sites that have already opened ticket sales — only future WordCamps and select existing WordCamp sites will be affected. We will reach out to the organizing team before making any changes to sites that are currently selling tickets.

If you notice any problems with Stripe transactions or other things in CampTix, please report them in the meta-wordcamp channel in WordPress Slack.

Camptix Notify functionality – documentation review

The task that was assigned to be at WCEU was to draft documentation for the Camptix Notify functionality of WordCamp sites, including some notes on the date format for the Purchased Date field in the filter conditions.

I’ve tried to keep the documentation as non technical as possible, but as a developer I would appreciate feedback from the rest of the community.

https://docs.google.com/document/d/12LP506qXGPOcwBNpsiThTavPwLptfJe4BILjMp7V5U0/edit?usp=sharing

I therefore ask anyone interested to review the document via Google Drive and leave your comments/suggestions on this post so that we can discuss changes or improvements.

I’d like to give this a two week deadline for comments until Friday the 13th (dun dun dun!) of July, in order to move the process of having this included into the WordCamp docs along promptly.

Thanks

#camptix, #documentation

Support for Community Team Mentors

According to @brandondove‘s excellent mentorship program report at today’s meeting, we have 27 deputies volunteering as mentors in total, with 19 people actively mentoring WordCamps. We hope to have a crowd of new deputies join the ranks once we launch the new deputy training materials early this year.

Both now and in the future, it’s been suggested that deputies could benefit from more peer support and communication with other deputies. Some suggestions for ways to put deputies more closely in touch with each other have included:

  • weekly meetings in #community-team slack
  • mentor hangouts
  • a private slack channel for deputies on wordpress.org slack
  • a public #community-mentors channel on wordpress.org slack
  • DM groups on wordpress.org slack

Do you have a suggestion, preference, comment, or concern? Let’s discuss!

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 support@wordcamp.org 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.

Recap of the Diversity Outreach Speaker Training meeting on July 11, 2018

Attending: @jillbinder, @miriamgoldman

Start:

https://wordpress.slack.com/archives/C037W5S7X/p1531328514000512

@jillbinder

  • We had one or two new sign-ups to run our diversity speakers training workshop since our last meeting.
  • I don’t think any new groups have run it.
  • We get most of our signups from the monthly Meetup newsletter. There have been fewer lately but usually at least one comes in. It’s been our best promotion so far so it’s worth always doing.
  • The other best way to get the word out so far is talking about it at WordCamps, so a reminder to please keep doing that.

@miriamgoldman

  • The schedule for WordCamp Montreal has been released, so I can talk about my talk now.
  • I’ll be talking about the importance of community, and how to get involved. When I get to the “get involved” portion, I’ll be talking about our team, and the important work we are doing, and how it helps the WordPress community evolve.
  • I’m hoping that I can get a case study to include. It’s a full length talk, so our team will get a significant feature.

@jillbinder

  • Seattle is an excellent case study. They ran our workshop many times last year in different parts of Seattle, and between that and other efforts that they made, they had the highest number of women speakers at WordCamp Seattle 2017. 60%!
  • And quite a few of them joined *our* team because they benefited from it so much they wanted to give back.
  • It would be worth interviewing them to find out what other changes happened in their community as a result.

@miriamgoldman

  • Oh, yes. Open call then to anyone on the team! Please contact me if you don’t mind being interviewed and having some bullet points featured in a WordCamp talk!

@jillbinder

  • Montreal too. They’ve been doing amazing work with the workshop for years and have had amazing results in their community. @zoonini is the contact for that, of course.

@miriamgoldman

  • That would actually make sense to tie in…since I’m speaking in Montreal. OK, will ping @zoonini later!

@jillbinder

  • Oh yeah, of course. Speaking in Montreal and talking about how this work affected *their* community.
  • It would be nice if we get new cities too… which brings me to my main agenda item for today.
  • We are close to being ready to start following up with Meetups to find out how the workshop went for them, and to collect some more info as well.
  • @dianewallace and @miriamgoldman will be on this for us. I’m just in discussion right now with @andreamiddleton about some of the bigger picture items about it.
  • So we have a draft of questions to send to the Meetups, but Andrea and I are talking about the purpose behind it and given the purpose, how to let folks know how it’ll be used and if it should be long-form email questions or short-form likert questionnaire questions.
  • I’m currently partial to keeping it long-form and informal. Part of what I think the purpose is is to give folks support and care after they have run it. We help them all the way up and them boom, drop them. But we want to hear how it went, what can be improved, etc.
  • Also global WordPress is interested in hearing about what kinds of changes do different regions need to make, which can inform other global WordPress initiatives.
  • So this is the current draft, and it is subject to change:

Hello!

We’re thrilled that you recently ran a Diversity Outreach Speaker Training and we would love to get some feedback from you on what worked and what we could improve.

1. Did you run it for a specific underrepresented group or for your general community? If a group, which one?

2. What worked well in the material provided?

3. Is there anything we could do to improve the material?

4. Did you find the workshop relevant for your region in the world? Did you have to change anything to make it work?

5. Finally, please feel free to give us any other feedback or ideas you would like to share we us.

Kind Regards,

The Diversity Outreach Speaker Training Team

  • I’m interested to hear what you think the bigger purpose should be, if you have any thoughts on that, anyone here or who is reading later.
  • I’ll likely defer to what @andreamiddleton thinks it should be, but it doesn’t hurt for us to think about it too. I sent her a proposal of my own thoughts, but that was right before this meeting so we haven’t discussed that yet.
  • But I was thinking that:

#1 (which group and what did they change for their region)
and
#4 (change for their region)

could be published for all,

and the rest would just be for our own info.
For example I heard from 2 groups early this year that slides were needed, so I made slides.

@miriamgoldman

  • Agreed. Maybe #5 if there is anything that would be worth sharing publically.

@jillbinder

  • So kind of an ongoing changes as needed as they make sense situation.

@miriamgoldman

  • 2-3 would definitely help us evolve the material. Which should always be evolving over time!

@jillbinder

  • Yes it should! Always be evolving. I can’t tell you how much evolution it has already gone under since we started it in 2013!
  • Ohh, maybe something about letting us know changes to the community, too. Like if speakers step up to be organizers and leaders.

@miriamgoldman

  • Agreed on the changes to the community! I’m a perfect example of that, lol

@jillbinder

  • Yes! Sooo wonderful, @miriamgoldman!
  • I also want to follow up with people in our team about their plans for running it, and if anyone wants to start training, or sitting in on train the trainers that @lswanson and I run.
  • Which is best done after they’ve run it themselves, but doesn’t /have/ to wait for that.

@miriamgoldman

  • I’m hoping to get started on training later this summer/early fall.
  • As for taking on a trainer role, from the train the trainers training I did, that will be around the same time

My focus is currently on WCMTL

@jillbinder

  • Yes of course. That is a big focus! And will be a big benefit to our team, too.
  • I believe @lswanson is still working on getting our Train The Trainers version of the workshop up online.
  • As posted yesterday, our meetings are now on the 2nd and 4th Wednesdays! https://make.wordpress.org/community/2018/07/11/slight-change-to-diversity-outreach-speaker-training-meeting-schedule/

@miriamgoldman

  • I’ve updated my calendar accordingly so I can send out reminders as appropriate!

jillbinder

  • Thanks for the great work you who is here and the folks who aren’t here today, many of whom are pushing things forward for us — mostly as discussed in the last meeting.
  • Next meeting in 2 weeks, on the 4th Wednesday. 🙂

 

End:

https://wordpress.slack.com/archives/C037W5S7X/p1531330302000056

#wpwomenspeak

Code of Conduct Survey

Our Code of Conduct survey is live!

The Community Code of Conduct project goal is to examine the potential of expanding the community team’s code of conduct for WordPress events, to include other spaces where WordPress contributors collaborate, including forums, websites, and official chat channels.

We have put together a short survey to help us assess what we need to be is where you come in! Please announce this survey to your meetup group, and share it as widely as you can within the WordPress community. The survey will be open until April 13, so please share it soon and don’t forget to take the survey yourself: https://18422602.polldaddy.com/s/community-code-of-conduct-survey

Local WordCamps in The Netherlands – Our experiences

In recent conversations with Hugh Lashbrooke, WordCamp organizers Remkus de Vries, Taco Verdonschot, Sjoerd Blom and Marcel Bootsman from The Netherlands shared their experiences. This is a summary of these experiences.

History

The first WordCamp in The Netherlands was in 2009. After that, five more WordCamps were organised, skipping 2011 and 2013 (because of the first WordCamp Europe in Leiden). During the last editions there was a discussion with WordCamp Central, now Called WordPress Community Support, about organizing local, city-based WordCamps in The Netherlands in favor of just one WordCamp The Netherlands.

Having organized six local WordCamps in The Netherlands, we were not sure if multiple WordCamps in The Netherlands was a good plan, also from a continuity point of view. In this post we share our experiences.

Local WordCamps

We’ve managed to organize a total of 4 local, city based WordCamps in the Netherlands so far. In 2017, two local WordCamps were organized, Nijmegen and Utrecht, followed by Noord-Nederland and Rotterdam in 2018. Currently Nijmegen and Utrecht are planned for 2018. Rotterdam and Noord-Nederland are in early planning phase for repeats.

WordCamp The Netherlands

The last WordCamp The Netherlands was in 2016. With a large increase of attendees (from 240 in 2015 to 407 in 2016) we managed to organize the largest WordCamp in The Netherlands ever, and bring the community together on a three-day event.

Difficulties with local WordCamps

With WordCamp The Netherlands, we offered the community a clear schedule, every year the community comes together on this nationwide event. Attendees, sponsors, speakers and volunteers could plan ahead for this one WordPress event in The Netherlands.

With the local WordCamps we are experiencing the following challenges:

  • Difficulties finding sponsors
    Sponsors were used to reserve a budget that they could use for one event, WCNL. In the current situation the sponsors need to divide that budget between four WordCamps, and also have the disadvantage of a smaller number of attendees, further lowering the ROI.
  • Attendees find it difficult to choose
    With the increased amount of WordCamps in The Netherlands, and in surrounding countries, we have heard from attendees that they find it hard to make a choice how to fit the WordCamps in their schedule, as there are quite some WordCamps in the area nearby (including Belgium and Germany). This puts pressure on the amount of people who can attend, which in its turn affects the willingness to sponsor these WordCamps.
  • Speakers have to choose
    Getting speakers to apply to speak at a WordCamp is a challenge in itself. When there are multiple WordCamps in the same small geographical region, this limits the possibilities for speakers to find a good fit in their calendar.
  • Volunteers
    A WordCamp relies on volunteers to run smoothly. When these volunteers need to make a decision on which WordCamp in The Netherlands they will attend, we expect to have trouble finding enough volunteers. Onboarding new volunteers is something that has high priority.
  • Financials under pressure
    Looking at the budgets and financial results of the four local WordCamps, we have to conclude that these are under pressure as well. A big loss for Rotterdam and small profits for the other WordCamps show us that for the next editions it could become more and more difficult to get a healthy financial result for all of them.
  • Target audiences
    With having multiple WordCamps in The Netherlands, we have a challenge to not make these WordCamps copies of each other. They need to be unique and have an overlap in target audiences. Only then will it be possible to have continuity with Dutch WordCamps on a regular, yearly basis.
  • Conclusion

    Given the experience we’ve gathered over the last 9 years, we think there is still a need for a nationwide WordCamp in The Netherlands. However, it has to offer the target audience something that local WordCamps do not offer, and it has to fit in the already busy WordCamp schedule in and around The Netherlands. Again, we’re a geographically small country (see map here). Additionally, to make a WordCamp The Netherlands interesting for sponsors, the number of attendees should be interesting enough to offer these sponsors a better ROI.

    Regarding the local WordCamps, we have seen quite a large number of people attend a local WordCamp for the first time.

    Credits

    This post is written by Marcel Bootsman (@mbootsman), and is based on input/feedback from Remkus de Vries (@defries), Taco Verdonschot (@tacoverdo) and Sjoerd Blom (@vertizio). Other members from the Dutch (and Belgian) WordPress community also gave their opinion about the current WordCamp setup: Monique Dubbelman (@boemedia), Benoit Gütz (@buxert), Bas Brader (@basbrader), Ruben Zwiers (@rubsel), Jeroen Rotty (@jeroenrotty), Wendy Weel (@wendyweel), Taeke Reijenga (@taeke), Simon van der Steen (@simonvdsteen), Luc Princen (@lucp). Thanks all!

Stripe is now available to all WordCamps

We just pushed out a big update to CampTix (the plugin for selling event tickets, written for WordCamp) on the WordCamp.org network. The main change is that Stripe is now included as a default payment method — until now it was a separate, beta plugin that had to be enabled on a per-site basis.

Stripe is a credit card processor that supports a lot of currencies, so this will allow WordCamps to support online ticket purchases in several places where we couldn’t before. For new WordCamp sites, Stripe will be enabled by default, instead of PayPal, though you will still be able to turn on PayPal if needed (the payment configuration for existing WordCamp sites won’t be affected).

WordCamps that already had the separate Stripe plugin enabled should experience a seamless transition.

You can see a full changelog of recent updates to CampTix here.

If you notice any problems with Stripe transactions or other things in CampTix, please post them in the meta-wordcamp channel in WP Slack so that we can troubleshoot them as quickly as possible.

Thanks to @vedjain, @andreamiddleton, and @iandunn for all of their work on this project, @dd32 for writing the original Stripe plugin for CampTix, and @indralukmana, @eliw, @imath, @JulienMelissas, and @juanfra for ideas and code contributions that went into this release.