Hosting Meeting Agenda – May 22nd, 2019

Hello all!

This is the agenda post for the meeting in #hosting-community on Slack that will happen at May 22nd, 2019 at 1700UTC.

Here is what we have so far:

  • Housekeeping
    • How is everyone adjusting to the meeting times?
    • We need your help with leading meetings and taking notes!
  • WordPress 5.2
    • How has rolling out the new version gone?
    • Site Health Rules
      • Any feedback from users about the Site Health check?
      • Have you seen any changes in support volume regarding the Site Health check?
    • Cryptographically signed WordPress updates
    • Anything else?
  • PHP Upgrade Workshop hosted in WordCamp Haneda in Japan
    • Hosts and volunteers helped conference attendees with updating to newer versions of PHP on each host’s platform
    • What do hosts think about promoting this kind of outreach during more conferences?
  • HostCamp (@sirjonathan)
  • We need your feedback about improving bulk upgrades (@jip)
  • Open Floor

Do you have anything else to add? Please leave a comment on this post! Look forward to seeing you there!

#agenda, #hosting-community

Hosting Meeting Notes: May 13, 2019

Here’s the summary of our meeting in #hosting-community on Monday, May 13, 2019 at 1400 UTC (Slack archive).

The agenda followed can be found here.

Attendees: @spacedmonkey @mazeheld @redituk @shinichin @miss_jwo @clorith @mikeschroder

Housekeeping

There’s a call for folks to lead and take notes for meetings. If you’re interested, please comment on this post! This is a great way to get involved and open to anyone that’s attended a few meetings.

A month has passed since the team started alternating meetings. How is it going?

@mazeheld noted that he thought maybe the Wednesday meeting was too early in the day.

@mikeschroder said he’d create a post on make/hosting to discuss, and collect some statistics for sharing after feedback is collected.

This has now been created — please read and comment on this post with how you think things are going.

WordPress 5.2 Check-in

Those present seemed to think the 5.2 release was well received.

@mazeheld brought up increased support due to Site Health Check. They made a support page specifically to address concerns surrounding it.

A couple of folks mentioned surprise that PHP versions < 7.3 result in a lost score, and that seeing a 100% score matters to customers.

Two ideas around it were to have recommendations (outside of requirements) separated from the “score” or to have some recommendations dismissable by administrators if they don’t apply to that user/environment.

There was a little confusion as to what themes are required to stay and/or be removed to have a perfect score.

PHP Upgrade Workshops

@shinichin shared about the PHP upgrade workshops that were run at WordCamp Haneda.

There was a room where hosts got together and gave presentations about how to upgrade with their panels, then a group of volunteers helped folks upgrade.

Around 50 folks got their sites upgraded!

As a result, they want to create documentation so that more meetups and WordCamps in Japan can do the same.

@miss_jwo will connect with @shinichin with documentation from the Site Health booth from WCEU last year, with the plan to do this at WCEU this year as well!

Feedback

If you missed this week’s meeting and have questions or feedback, leave a comment on this post and share your thoughts! OR….Come join for the next meeting!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, May 22, 2019 at 1700 UTC. Hope to see you then!

+make.wordpress.org/updates

#weekly-hosting-chat

Meeting Time Check-in

Hi Everyone!

It’s been just over a month since we started trying a new meeting timetable, alternating between Mondays at 1400 UTC and Wednesdays at 1700 UTC.

How is it going for folks?

In retrospective terms:

  • What worked well / the team should continue doing?
  • What didn’t work / the team should stop doing?
  • What should the team start doing?

General feedback that doesn’t fit into the above is fine as well.

Please comment on this post for feedback!

#hosting-community

Hosting Meeting Agenda – May 14, 2019

Hi everyone!

This is the first agenda post, for the meeting on May 14, 2019 at 1400 UTC that will happen in #hosting-community on Slack.

Here’s what I have so far:

  • Housekeeping
    • Check in on how meeting times are working
    • Request volunteers for running meetings and notes
  • WordPress 5.2
    • Check-in: How’s the new version going?
    • Site Health Rules
    • Anything else?
  • PHP Upgrade Workshop (@shinichin)
  • Open Floor

Do you have anything else to add? Please leave a comment on this post! Look forward to seeing you there!

#agenda, #hosting-community

Hosting Meeting Notes: April 29, 2019

Here’s the summary of our meeting in #hosting-community on Monday, April 29, 2019 at 1400 UTC (Slack archive).

Attendees: @mikeschroder @javiercasares @mazeheld @kenshino @sanyog @mikeschinkel @redituk @shinichin

Hosting Meeting Notes

The idea of posting an Agenda post prior to the meetings was recommended and folks present seemed to support the idea.

Reasons given included:

  • Helpful for letting folks who can’t attend bring things up async.
  • Developing habits to better documentation is beneficial for future folks when more things are going on..

@mikeschroder is going to chat with @jadonn about this.

@kenshino suggested having statistics in the meetings would help growing the team. Polyglots team does this (Slack link).

Polyglots sharing statistics on meetings

We need to figure out what sorts of metrics would be interesting to know. These ideas were given:

  • @kenshino: How many hosts are working with the team
  • @javiercasares: PHP versions, Database versions, and some of the statistics at wordpress.org site
  • @mikeschroder: WP.org knows how the PHP version numbers shift between hosts. We haven’t mentioned them to avoid shaming hosts. It would be great to use these to incentivize upgrades. details on hosts that have had success/a large amount of upgrades to new versions?

@shinichin noted that there’s a difference in how hosting providers are involved among countries. Some feel that they are part of the community and others don’t see that way.

We didn’t have the time to discuss:

  • WordPress 5.2
  • Idle Hosting Test Runners

@shinichin raised a topic for the next meeting: “PHP version update workshop at WordCamps”

@mikeschroder mentioned two things related to 5.2:

  1. @clorith posted this Site Health dev note to the chat late last week (thank you!!): https://make.wordpress.org/core/2019/04/25/site-health-check-in-5-2/
  2. 5.2 got pushed back by a week, and is now being released on the 7th: https://make.wordpress.org/core/5-2/

Feedback

If you missed this week’s meeting and have questions or feedback, leave a comment on this post and share your thoughts! OR….Come join for the next meeting!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, May 8, 2019 at 1700 UTC. Hope to see you then!

+make.wordpress.org/updates

#weekly-hosting-chat

Hosting Meeting Notes: April 24, 2019

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

Attendees: @jadonn @brettface @jnash @andrewtaylor-1 @amykamala @riper81 @mazeheld 

WordPress 5.2 Release – May 7th

The release of WordPress version 5.2 has been pushed back to May 7th. More information found here:

WordPress 5.2 Beta Testing

Hosts: Please test WordPress 5.2 beta before it releases.

WordPress 5.2 is currently set to release with the new Site Health tool.

Check out this doc that has details on tests and filters for the Site Health tool.

Please note that some tests may not apply, or may require changes for certain hosts, so please take a look! For example, there’s a check for automatic update support that requires that WordPress be writable and not have a .git directory. Hosts that have a non-writable WordPress directory or native version control and handle upgrade for users manually may want to change or remove that test using the available filters.

Some more info can be found on WordPress 5.2 beta here: https://wordpress.org/news/2019/04/wordpress-5-2-beta-3/

Automated Unit Testing

Some Hosts have reported issues with the automated unit testing tools:

Please continue submitting test results. Thank you to all who have participated thus far!

Hosting Metrics Tracking

@andrewtaylor-1 suggested tracking how PHP version offerings across hosts change with the new requirement of 5.6 and up in WordPress 5.2 by grabbing a baseline before 5.2 and then again at 30, 60 and 90 day intervals.

If hosts are unable to gather those metrics by the release of 5.2, any information on adoption rates for newer versions of PHP are welcomed.

It was noted that many hosts started enforcing use of PHP 5.6 and higher prior to the new WordPress 5.2 PHP requirement being issued.

Feedback

If you missed this week’s meeting and have questions or feedback, leave a comment on this post and share your thoughts! OR….Come join for the next meeting!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, May 1st, 2019 at 1700 UTC. Hope to see you then!

+make.wordpress.org/updates

#weekly-hosting-chat

X-post: 5.0 Release Retrospective Wrap Up

X-comment from +make.wordpress.org/updates: Comment on 5.0 Release Retrospective Wrap Up

Hosting Meeting Notes: April 15, 2019

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

This was the first meeting at the alternate day/time, and I’m excited to see so many folks!

Attendees: @javiercasares @tylerthomas @j-falk @clorith @boborchard @danfoster @redituk @arvindsingh @katebolin @earnjam @brechtryckaert @mazeheld @tnash @mikeschroder

Hosting Meeting Notes

@redituk noted that he wasn’t able to review meeting notes, so we chatted briefly about the need for folks to review notes/lead meetings and enable that.

@mikeschroder noted that permissions were something we could add, but also that public previews could be enabled if make/hosting had the proper plugin. Since the meeting, this has been added so that anyone can review. Thanks @dd32!

Site Health

As a followup on the chat from last week @mikeschroder suggested folks test the 5.2 beta and linked to a doc that has details on tests and filters for the Site Health tool that is set to ship.

Specifically, he noted that some tests may not apply, or require changes for certain hosts, so please take a look! For instance, there’s a check for automatic update support that requires that WordPress be writable and not have a .git directory. Hosts that have a non-writable WordPress directory or native version control and handle upgrade for users manually may want to change or remove that test using the available filters.

@earnjam pointed out that there will also be a post on make/core soon regarding Site Health.

@j-falk asked if there was any documentation on the PHP modules that Site Health checks for availability. This may be in the upcoming dev note, but in the meantime, it’s visible in the hosting handbook and in the Site Health source.

@mazeheld noted that Site Health was working well for them.

Hosting Automated Testing

@redituk asked to discuss the hosting automated tests.

@earnjam explained that when he set up the tests for Bluehost recently, there were a couple of things he noticed.

First, reporting of the specific error encountered stopped working when the autosave endpoint was merged to core. This makes it so that we can no longer see which tests failed on a host from make/hosting.

Fixing this will involve changes both in the test reporter and on the meta side, but there is currently no way for hosts to know when the test runner/reporter needs to be updated. This makes it difficult to get hosts up to date.

Secondly, some tests were added to core that were failing on hosts that run the tests as root and were since removed temporarily.

He said he’d check to find out which hosts we should contact and recommended we document that the tests should not be run as root (this documentation has since been updated).

Feedback

If you missed this week’s meeting and have questions or feedback, leave a comment on this post and share your thoughts! OR….Come join for the next meeting!

Next Meeting

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

+make.wordpress.org/updates

#weekly-hosting-chat

X-post: The Get Involved table at WCEU 2019

X-comment from +make.wordpress.org/community: Comment on The Get Involved table at WCEU 2019

Hosting Meeting Notes: April 11, 2019

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

Attendees: @brechtryckaert @FahimMurshed @tnash @brettface @mazeheld @jnash @zzap @redituk

New Meeting Times Decided

There was brief discussion around the decision to test alternating meeting times for a month.

If you’re interested in taking notes or helping lead either meeting, please leave a comment either here or on the meeting-times-post!

Folks were positive, with @redituk pointing out it would be a good idea to remind folks when the next meeting is, in addition to the make/meetings schedule.

WCEU Contributor Day

@zzap asked if anyone was interested in representing the Hosting team at WCEU, and @mazeheld volunteered. Thanks!

Site Health

@jadonn shared a doc from @mikeschroder detailing the Site Health checks and some filters available for them targeted for WordPress 5.2. Please take a look and see if they look appropriate for your hosting environment. @clorith noted that a dev note is coming soon as well — thanks!

Feedback is appreciated!

Feedback

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, April 24th, 2019 at 1700 UTC. Hope to see you then!

+make.wordpress.org/updates

#hosting-community, #weekly-hosting-chat