Hosting Meeting Notes: January 23, 2019

Here’s the summary of our meeting in #hosting-community on Wednesday, March 6, 2019 at 1800 UTC (Slack archive).

Attendees: @jadonn @brechtryckaert @j-falk @mikeschroder @abdullahramzan @brettface @dhsean @francina @joostdevalk @dyrer @gziolo @dws122

Meeting Introduction

The proposal was made to open each hosting-community meeting with an introductory text. @mikeschroder has written following text as a proposal:

If you’re new here, welcome! Feel free to introduce yourself if you like!
This is the weekly meeting for the Hosting community team, and we work together to help make user experience with WordPress better at hosts. Many folks on the team are from hosts, but there are also some learning to host WordPress themselves, or that work in the community with hosts, like plugin and theme authors, or folks that work in support.
This meeting is usually used to connect about WordPress happenings throughout the week connected with hosting and to catch up on the status of the team’s ongoing projects. Usually we’ll step through a few scheduled items, then open up the floor at the end for any additional topics to be discussed. Notes are taken during the chat for posting on [].

While the consensus of the meeting attendees deemed the text good as-is, @jadonn indicated that other submissions are welcomed. He will create a blog post on the intro-text and make a final call for feedback, before this text will be taken into use.

Quick Bug Report

@jadonn brought following bug to the attention, which impacts hosts using cPanel and could prevent plugin updates due to broken symlinks:

End-To-End (E2E) Testing

@j-falk raised the question if there was any interest in the group to work on this together, possibly providing a benefit for both hosts and site owners.
@mikeschroder and @j-falk both indicated to be able to invest time into E2E testing. @j-falk will take this up with @gziolo from the core-editor channel.

Video-based Meeting

@brettface proposed February 5th, 21:00 UTC as the date and time for the first video meeting using Zoom. @francina will help provide the platform. The link will be shared as we approach that date.

Showcase Redesign

@Joostdevalk asked for feedback on, since the marketing team plans on highlighting agencies and hosts more. @dws122 raised the question what criteria the showcase entries are selected on. @j-falk inquired about the review process and @javiercasares proposed reviewing these entries at contributor days. @joostdevalk also indicated to be considering internationalization. He will also today’s feedback into account and requests to leave further thoughts at the post.

Our Strenghts and Challenges

@jadonn requests to provide feedback on the post by @chanthaboune.


Miss this week’s meeting and want to know more about anything above? Spend some time in the comments and share your thoughts! OR….Come join us!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, March 13th, 2019 at 1800 UTC. Hope to see you then!


Video Chats and Herding Cats


One idea to come out of last month’s WordCamp US was the understanding that the Hosting group could be so much more active, if only we could boost our participation numbers.

The Hosting group is full of smart, well-connected people that either work at web hosts, or work closely with them in various capacities. And, despite nearly 600 members in the #hosting-community Slack channel, check-ins at our weekly meetings (Wednesdays at 1800 UTC) rarely top more than a half dozen active participants.

WordCamp Energy!

As anyone who has attended a WordCamp can tell you, the value of face-to-face interactions is immeasurable. Many people will become much more engaged in a topic when discussing it in real-time, in the real world. Of course, the reverse is true as well – many people feel more comfortable communicating online. That’s fine, too!

One of the things the Hosting group discussed at WordCamp US’ Contributor Day was a desire to capture that high enthusiasm level that exists at WordCamp events and…bottle it! We wanted to bring it online in a way that Slack, for whatever reason, isn’t always able to fully replicate.

What’s next?

The idea we came up with wasn’t particularly revolutionary: video chats.

We would like to experiment with augmenting our regular, standing Slack meetings with group video chats. Our Slack meetings will never go away. Our video chats might. 🙂 This is really just a test to see if we can boost engagement among our group members.

The goal is purely to give this group another outlet for communication in a method that may be more comfortable for some participants to engage in, at a time that’s a bit separated from the Slack meetings.

We’re still working out the technical aspects of it all, but either recordings, transcripts, or meeting notes would be made available shortly after the video meetings. @francina has kindly offered up the use of a Zoom account for us to use while we give this a shot.

Let’s Do It!

I’d like to propose a meeting time of 2100 UTC on Tuesdays with our first trial call on February 5, 2019 2100 UTC.

We will share links to the meeting in #hosting-community as we get closer to the date.

With all that said, we’d really love to see you there! This could be great! Or super lame! I guess we’ll find out!

X-post: Our Strengths and Challenges

X-comment from Comment on Our Strengths and Challenges

Hosting Meeting Notes: January 16, 2019

Here’s a summary of the meeting in #hosting-community on Wednesday, January 16, 2019 at 1800 UTC (Slack archive).

Attendees: @rawrly @desrosj @brettface @JavierCasares @j-falk @ronc9 @designsimply @aaroncampbell @francina @mikeschroder @brechtryckaert @andrewtaylor-1 @clorith

Communication and Decision-making Processes

We discussed @francina‘s post with proposals on team communication and decision-making. Listed here are the parts that were discussed during the meeting.

Adding a standard introduction to the group and the purpose of meeting at the beginning of each chat

There was positive feedback for this idea, so @mikeschroder will work on an introduction to the group — if you have any recommendations for this, please comment on this post, as help is appreciated.

Giving video chats a try

Last week, it was decided to go ahead and give regular video chats a try. This will be in addition, and not as a replacement, to the group’s regular text chats.

@brettface is going to give facilitating these a go, and said that he’d have a post on this blog with information about the video chats before next week.

@francina mentioned that as long as the timing doesn’t conflict with the community team’s deputy meetings, we can share that Zoom account.

Posting or cross-posting notes to updates P2

@mikeschroder noted that he has gone ahead and started crossposting them.

Should we make all team decisions here in the P2?

Folks in the chat were mixed on whether it was a good idea to move all team decisions to this P2. In general folks seemed to prefer moving some larger decisions here, while still making smaller decisions in Slack, or having discussions on the P2 to allow for wider input, then finalizing those decisions in Slack.

@mikeschroder noted that this would require more posts, and help was requested both for reviewing and writing if anyone was interested. @brechtryckaert and @j-falk offered to help out, and have been added to the P2 (Thank you!).

IIS Gutenberg Uploads Bug

There’s a bug that is affecting uploads in Gutenberg on IIS, causing them to error. If you are running into problems with this, or are interested in helping out with a fix, please comment or add a PR on this Gutenberg issue.

Open Floor

WordPress version in database?

@aaroncampbell asked the group if it’d be helpful to have the WordPress version in the database for querying/finding WordPress versions without having to read the filesystem. Most folks in the room noted that they’d been using WP-CLI for these purposes. If you’d find this useful, please comment on this post! If there are a few hosts it would help, a ticket can be opened.

Hosting plans for PHP widget/notice

@j-falk asked the group how they’d planned to approach customization of the PHP update notification widget that is coming in WordPress 5.1.

He noted that there’s an environment variable for changing the link for hosting information, but is interested in notifying users based on higher versions of PHP to get them upgraded earlier.

@mikeschroder said he’d had similar feedback and posted it as a comment on that P2 along with some additional notes. @flixos90 followed up with a reply to these concerns and ideas, inviting everyone in the room to the PHP group’s next meeting on January 21, 2019 at 1600 UTC.


@JavierCasares is looking for feedback on a wp-config.php generator he made.


As noted above, @brechtryckaert and @j-falk are the newest folks helping out with this P2. If you’ve been attending meetings for a little while and are interested in helping review or write posts, please DM @mike or @jadonn on Slack.

Miss this meeting and interested in connecting on what was discussed? Let’s chat! Please leave a note here in the comments or in Slack!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, January 23, 2018, 1800 UTC. Hope to see you then!


Hosting Meeting Notes: January 9, 2019

Here’s a summary of the meeting in #hosting-community on Wednesday, January 9, 2019 at 1800 UTC (Slack archive).

Attendees: @jadonn @fahimmurshed @brettface @miker @dhsean @t-rave @JavierCasares @j-falk @magwp @francina @aaroncampbell @brechtryckaert @dws122 @desrosj @mikeschroder

As mentioned in the chat, WordPress 5.0.3 has been released! Please feel free to comment here or reach out with feedback in #hosting-community if you run into any issues.

5.0 Followup

Following @clorith‘s request last week, feedback was requested about how hosts that had delayed updates until the new year have been finding the 5.0 upgrades in the new year.

One unmanaged host mentioned that users have been reporting a significant amount of breaking sites, so they’ve been recommending upgrades, but with the Classic Editor plugin installed until everything has been updated for 5.0 compatibility on a site. They mentioned they were willing to watch out for trends on plugins and themes that cause breakages, and that it seems to usually be ones not found in the repo.

Marketing Team Howdy

@miker from the Marketing team dropped by to connect with the team. He offered help from the Marketing team, and mentioned that he plans to attend regularly to help with cross-team communication. Thanks, and welcome!

Communication and Decision-making Processes

We briefly discussed @francina‘s post with proposals on team communication and decision-making.

@brettface offered to facilitate giving video chats a try, pending technical assistance by someone who has access to whatever platform the team will be using. @mikeschroder offered to assist there as needed, and mentioned that @aaroncampbell also offered to do so in a past meeting. @francina is checking to see if there’s a Community team Zoom account that’d be appropriate for the hosting team to use as well.

@brettface will be drafting up a post for this blog with next steps.


Please leave feedback on @francina‘s post with proposals on team communication and decision-making.

Other things you’d like to connect on? Please leave a note here in the comments or in Slack!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, January 23, 2018, 1800 UTC. Hope to see you then!

X-posting: Site Health Check Project review at WCUS

Hosting Meeting Notes: January 2, 2019

Here’s a summary of the meeting in #hosting-community on Wednesday, January 2, 2019 at 1800 UTC (Slack archive).

Attendees: @clorith @andrewtaylor-1 @dws122 @desrosj @mikeschroder @fahimmurshed

This was a light meeting, with many folks still out following the new year.

5.0.2 and 5.0 Followup

@mikeschroder asked how things were going following the 5.0.2 release, with @clorith noting nothing major.

@clorith requested feedback from hosts that had delayed upgrades of 5.0 until the new year. If this is you, please let us know how things are going in the comments or in #hosting-community in Slack!

Communication and Decision-making Processes

@francina made a wonderful post on this O2 about communication and decision-making, sharing learnings from the Community team.

@mikeschroder requested feedback on this in the meeting. Some of the items listed are tactical, like posting/cross-posting updates to the updates O2, which can be done immediately.

Others are proposals that would be great to have feedback. Please read it and leave comments with your thoughts!


Miss this week’s meeting and want to discuss the things chatted about? Please leave a note in the comments or in Slack!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, January 9th, 2018, 1800 UTC. Hope to see you then!

On chats, video chats, recaps and decisions

During the last chat we discussed a number of possible changes to the group chats.
Here is my experience from the Community Chats over the past few years


Sometimes not a lot of people show up, but consistency is key.

Another tip: we shouldn’t assume everyone is familiar with what we do in any team so we start by making a short intro.
This is what we post, it fits what we do and how we do it.

Hello hello

We’re starting our bi-monthly Community Team chat now – react to this message with your flags so we can see where you’re all from!

For anyone who is joining for the first time (whether active or observing), this is a meeting where community deputies discuss issues that have come up, WordCamps/meetups they are working on, and generally keeping up to date on what is going on in this corner of the WordPress project.

Most contributors on this team are volunteers, but we do have a handful of people who are sponsored to do this work. Ask questions as you have them, but remember we are family-friendly around here.

We might discuss issues when meeting in person, but we make decisions on the community blog :slightly_smiling_face:

Video Chats

It was discussed to add a video call to the regular weekly chat.
The main doubt seems to be how to make the content of those chats available for posterity: Zoom has the option to record video calls and they can be posted on YouTube or
I will check if the Community Team has a paid account and will report back.

Chat recaps

Team reps should post chat recaps in the Updates blog.
For the Community Team I post them there (Admittedly quite late) and then post the link to the Updates post in the agenda post in the team blog. See example.
Another solution is cross posting.
Whatever we pick, it would be great to see the hosting-community chat recaps show up in Updates 🙂

Discussions and decisions

The Community Team is operating in full transparency, which means that we discuss in our blog all the issues that come to mind.

We are refining the procedure, also by trying to use titles that make it clear from the start what you are about to read. If it’s a proposal the title will be “Proposal: …”, if it’s an announcement “Announcement:…”, if we need to put a team together for a specific purpose or need help with a task “Volunteers needed:…”, you get the gist.

If action is needed, we set a deadline at the end of the post and mark it as “To Do” through the native O2 functionality. See example.

Finally, when you want to wrap things up – even to say “We couldn’t come to a conclusion but we exhausted the conversation – you can use the “Top Comment” function.
When you click to edit a comment you will see “Edit, Delete, Top Comment”.
This last item will

  • Color the background of the comment in green
  • Show it as a sticky comment on top of the others

This is a great visual way to see where you’re at, when scrolling through the blog. You can also mark the post as “Done” if you want to make super-mega sure that everyone sees it 🙂 See example.
If you don’t see this in the blog, you need to ask Meta to activate it.

X-posting: PHP Meeting Recap – December 17th

Hosting Meeting Notes: December 12, 2018

Here’s a summary of the meeting in #hosting-community on Wednesday, December 12, 2018 at 1800 UTC (Slack archive).

Attendees: @brettface @akpanpromise @dws122 @antpb @mikeschroder @boborchard @stevenkword @mclancy3 @dhsean @pbiron @javiercasares @clorith @andrewtaylor-1


There’s been great feedback on how both plans and how things are going with 5.0 rollout within the channel! Thanks everyone! 


The meeting started out with folks chiming in on how the WordPress 5.0 release has been going so far.

By and large, there has been much less support than expected after the release. So far, it’s widely seen by hosts as going well.

Users reporting issues seem primarily to be due to plugin or theme incompatibilities, with one host reporting confusion around Twenty Nineteen, which is being investigated.

@pbiron offered to make public and collaborate on a list of Gutenberg compatible plugins and themes that his team is working on. If anyone is interested, please comment here, or message in Slack!

There was discussion on documentation in general, that included @antpb pointing out that the Docs team has made a call for contributors for Gutenberg documentation, and later on @javiercasares offered to share a technical manual as a proposal for further documentation for the handbook.

WordCamp US

Many folks from the hosting community team met during WordCamp US. @brettface synopsized from the public notes made during WordCamp US contributor day. I love how the meetings were documented in real time and suggest taking a look at them to get a better picture of the discussion.

Mission and Direction

In general, a lot of the conversation was around direction of the team, and the best ways we can work together and invite others into conversations around hosting WordPress.

By the end, the group gathered came up with a suggestion for a new mission statement, with the aim of being more inclusive.

Work to improve the WordPress’ end-user experience across a variety of hosting environments through a combination of industry collaboration and user education.

What do folks think about that? Let’s bounce this back and forth a little, and decide on a new one.

There were suggestions to have a regular video meeting as an additional gathering to help with connections. What do you think about this? 

Another theme in the conversations I had was around folks that wanted to share information or data, but feel uncomfortable doing so publicly — or at least without anonymity, with one person suggesting a private channel for that use. I’m happy to anonymize any information for meetings if you feel comfortable, but does anyone have additional ideas to help folks feel more comfortable participating in regular chat and meetings?

Site Health Check

The hosting team met up with the Health Check / Servehappy teams to discuss direction and the newly announced initiatives to merge them during the next year and increase the PHP version requirement for WordPress.

The aim is to ship WSOD (PHP Fatal Error) protection and an in-dashboard PHP version warning for PHP < 5.6 in WordPress 5.1, planned for February 21, 2019.

You’ll start seeing the updates related to the above projects cross-posted on this blog so that it’ll be easier for everyone to stay connected.

See more in the notes.


Miss this week’s meeting and want to discuss the things chatted about? Please leave a note in the comments or in Slack!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, December 19, 2018, 1800 UTC. Hope to see you then!