Survey: Weekly Meeting Schedule

As seasons change, the warmer locations in the world experience longer day-time and the comparatively cooler locations experience longer nights, which brings the popular concept of DST (daylight saving time) into the conversation for the Hosting Team. Typically countries move their clocks forward one hour during summer and spring, and countries in autumn or winter seasons turn their clocks back one hour to save as much daylight as possible.

The hosting team currently has two weekly meetings, one at 09:00 UTC and another at 18:00 UTC to provide a wider coverage for contributors from all over the world. The first meeting time is more convenient for folks in regions such as APAC (Asia / Pacific) + EMEA (Europe / Middle-East) and the second meeting time is more convenient for folks in regions such as EMEA + AMER (America).

Taking into account that APAC time zones generally do not change times for daylight savings, but that Europe and America do:

Should meeting times be adjusted for daylight savings?

Here is a quick example of the current situation as DST takes into effect in a few weeks (note: some countries have already made changes and others will do so on the weekend of October 24 or later).

The idea would be to apply the changes by Wednesday, October 28. The proposal is to consider whether to adjust to a better time or not (compared to the current local time).

Meeting 09:00 UTC

09:00 UTC
After DST
09:00 UTC
After DST
10:00 UTC
Wellington (NZ)22:0022:0023:00
Tokyo (JP)18:0018:0019:00
New Delhi (IN)14:3014:3015:30
Moscow (RU)12:0012:0013:00
Berlin (DE)11:0010:0011:00
London (GB)10:0009:0010:00
Some timezone for meeting at 09:00 UTC

Meeting at 18:00 UTC

18:00 UTC
After DST
18:00 UTC
After DST
19:00 UTC
Berlin (DE)20:0019:0020:00
London (GB)19:0018:0019:00
Brasilia (BR)15:0015:0016:00
New York (US)14:0013:0014:00
Los Angeles (US)11:0010:0011:00
Honolulu (US)08:0008:0009:00
Some timezone for meeting at 18:00 UTC

Which schedule works best for you? Do you prefer to keep the meetings at 09:00 UTC or should we move them to 10:00 UTC?

For the second meeting do folks prefer to stick to 18:00 UTC or should we change it to 19:00 UTC?

Please feel free to drop a comment with your preferred option for either meeting, or both. Your feedback is valuable!

Hat tip to @javiercasares for writing this post and @chaion07 for the peer review.

#meeting-time, #meetings, #survey

Hosting Chat Recap: Wednesday, August 19, 2020

Here’s the summary of our meetings in #hosting-community on Wednesday, August 19, 2020 at 0900 UTC and on Wednesday, August 19, 2020 at 1800 UTC. (Slack archive).

The meetings were led by @mikeschroder and @jadonn. Notes taken by @Crixu.

Attendees: @chaion07, @clorith, @hristo-sg


## Greetings
Welcome and Check-in
New Contributor Call Out

## Highlights
WordPress 5.5 Check-in

## Hosting Team Time
WordCamp US / 24 Hour Contributor Day

## Open Floor / Work Time


WordPress 5.5 Check-in

During the meeting on Wednesday, August 12, 2020 some issues were raised which appeared with the release of WordPress 5.5. This week we checked back with the hosting team members to see if they got solved and if new ones appeared. @mike brought up the following issues:

In general it looks like the removal of jQuery Migrate was a bigger deal then expected.

As a reminder, the support team is maintaining a “Read first” list here:

Hosting Team Time

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US / 24 Hour Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus.

WordCamp US 2020 won’t take place as planned before but the team is looking into an 24 hour online Contributor Day. Last week we saw a few people raising their hands to volunteer, help, or simply attend. If you want to join the hosting team on the 24h CD drop by the slackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel 🙂

Open floor

As the Servehappy recommendation for PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. versions was moved forward, @clorith asked the attendees on how they are dealing with PHP version migrations.

#hosting-community, #meetings

Hosting Chat Recap: Wednesday, August 26, 2020

Here’s the summary of our meetings in #hosting-community on Wednesday, August 26, 2020 at 09:00 UTC (Slack archive) and on Wednesday, August 26, 2020 at 1800 UTC (Slack archive).

The meetings were led by @mikeschroder and @jadonn. Notes taken by @javiercasares.

Attendees: @chaion07, @Crixu, Mark Muyskens, @amykamala, @piotrekkaminski, @davidvee, @asmartbear


## Greetings
Welcome and Check-in
New Contributor Call Out

## Highlights
Call for volunteers for WP a11y day
WordPress 5.6 Kickoff
Apple, Google, and Mozilla SSL/TLS certificate policy changes
Learn WordPress is Live

## Hosting Team Time
Dropping support for old PHP versions in a fixed schedule

## Open Floor / Work Time


Call for volunteers for WP a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( day

There’s a call for volunteers open for WordPress a11y day!

@mikeschroder invites everyone from the team to join.

The event itself will be for 24 hours, and held on Friday, October 2, 2020.

WordPress 5.6 Kickoff

WordPress 5.6 kicked off last week, and is the final release of the year for WordPress. It is currently scheduled for release on December 8th, 2020.

@mikeschroder encourage everyone to give it a read.

Apple, Google, and Mozilla SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server./TLS certificate policy changes

It was said that commercial certificates usually are for 1 year, and Let’s Encrypt for 3 months, and the main concern is for internal or service organization certificates.

Learn WordPress is Live

Community and Training teams have launched a new platform for online learning for WordPress – Learn WordPress!

Hosting Team Time

Dropping support for old PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. versions in a fixed schedule

On July 24, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team brought up a proposal to drop the support for older PHP versions via a fixed schedule.

There have been several proposals and comments. Premises and data that have come to light (context):

  • PHP: bump minimum version requirements #51043
  • Key WordPress Statistics
  • A lot of hosts give from PHP 5.4 to PHP 7.4 (at least, from PHP 5.6 to PHP 7.4)
  • One thing is core, and another are plugins and themes
  • Plugins and themes may need a “tested up to” PHP version #51139

Mark Muyskens has explained that he is against a fixed schedule. “Too many folks out there drag their feet as far as updating it, unless forced by the host. What do propose when a customer doesn’t switch off PHP 5 for example when support is dropped? Blocking core updates? That’s going to lead to other larger problems.”

@javiercasares made a lot of proposals. First, WordPress should be in line with PHP (those are example on how it should be on older versions):

WordPress 5.6 = PHP 8.0 (dec 2020) -> supports PHP 8.0 – 7.2
WordPress 5.3 = PHP 7.4 (dec 2019) -> supports PHP 7.4 – 7.1
WordPress 5.0 = PHP 7.3 (dec 2018) -> supports PHP 7.3 – 7.0
WordPress 4.9 = PHP 7.2 (dec 2017) -> supports PHP 7.2 – 5.6
WordPress 4.7 = PHP 7.1 (dec 2016) -> supports PHP 7.1 – 5.6

So, WordPress (as a Community) should give info on WordPress (major) versions and PHP (major) versions supported. For example: WordPress 5.5 supports PHP 5.6.20 to 7.4. @mikeschroder considers that this could be in the Hosting Handbook.

In summary, each major WordPress version should officially support the PHP versions supported in that time (+/- 1 version), also, create a table with supported versions, so anybody knows the limits in each version.

@mikeschroder like the idea of scheduling, so that hosts (and users) can know what to expect. The actual schedule being up for debate is great. Also, love to discuss how hosts can help with the issue that is the background of this particular proposal, how can we best work together / with the project to get folks upgraded — not just from the 5.x, but in the future.

@jadonn highlighted that some hosts’ platforms’ PHP versions are provided by cPanel, Plesk, or the software managing the platform. In that case, the host is beholden to cPanel or whoever provides the PHP binaries.

@asmartbear “The good thing about a fixed schedule is it’s easy to plan for, way ahead of time. Tech, customer comms, measuring potential impact, etc…”. “A bad thing is you can’t use judgement calls.”

“It could be helpful for Core to mandate things, because it’s a forcing function for action, which doesn’t “blame” the hosts. So that might be net-positive for all hosts.”

“I think the main tension is that increasing PHP requirements is what’s best for the entire project/community from a technical perspective (features, performance, security, modernity), but anything that causes friction for users moves us away from the goal of “51% of the web.”

piotrekkaminski: “Support will either have to deal with PHP issues or sites getting hacked. My personal POV is i would rather take PHP issues.”

@jadonn: “It is probably a worthwhile question to ask about what is the path to the 51% goal. Is enforcing a newer version of PHP the path to achieving that goal? Like how does the PHP version correlate to or drive WordPress adoption.”

With that in mind, we left the meeting asking if there is a possibility to have more correlated data to make that kind of decisions.

@asmartbear closed with: “To Democratize Publishing doesn’t just mean that you can publish, it also means you own your work, which in the Internet world, means owning your site, and the wider ideals of the Open Web as well. No one wants to do maintenance, and many people (most?) don’t understand it. I believe we should be part of the solution, helping them along, rather than telling them to go to some closed-sourced, closed-web system. Also I think you’re not considering the fact that it’s not necessarily even the site owner’s “fault” in a certain sense. They use / bought some pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party or theme years ago and now it won’t work. Now you’re saying they have 4 months to replace their theme “or else.” While there is merit in that forcing function, our attitude should be one of compassion and trying to find the best way forward, rather than saying to a non-technical site owner that they should go re-tool a theme or else take their site.”

Next Meeting

The next meetings will be in the #hosting-community channel on Wednesday, September 2, 2020 at 0900 UTC and Wednesday, September 2, 2020 at 1800 UTC. Hope to see you then!


Hosting Chat Recap: Wednesday, July 01, 2020

Here’s the summary of the meeting in #hosting-community on July 01, 2020 at 09:00 UTC and on July 01, 2020 at 18:00 UTC.(Slack archives).

The meetings were led by @mikeschroder and @jadonn. The Notes were taken by @chaion07.

Attendees: @tillkruess, @ugyensupport, @decipher05, @chaion07, @GMSamejo, @javiercasares, @pfefferle, @francina, @Crixu, @mikeschroder, @jonathansulo, @jadonn, @amykamala, @fahimmurshed, @passoniate, @evanstanton.

At the beginning of the meeting, there was a discussion about the requirements for getting a hosting team badge. Details on this can be found in the hosting handbook. If you have any questions, or are missing a badge, please leave a comment on this post, or contact any of the team reps!


## Greetings
- Welcome and Personal Check-in

## Highlights
- WordPress 5.5 Beta 1 upcoming
- jQuery update

## Hosting Team Time
- PHP 8 and Hosting Tests- Task Check-in
- Open Handbook PRs

## Open Floor


WordPress 5.5 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1

WordPress 5.5 Beta 1 will be released on 7 July 2020!

5.5 will be the second major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. of 2020 and aims to include an update of the block editor to the latest release of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc., automatic updates for plugins and themes, a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. directory, XML sitemaps, and lazy loading of images.

@pfefferle and @javiercasares mentioned that testing has been going well so far.

jQuery Update

jQuery is getting a major update this time around, and testing has been requested.

@javiercasares pointed out a plugin that makes it easy to test.

Hosting Team Time

Host Testing and PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. 8.0

@pfefferle brought the hosting tests and PHP 8 up for discussion, specifically: “How we can effectively test and report PHP 8 problems and does it make sense to change the host tests to PHP 8 when development of 5.6 starts?”

@mikeschroder recommended that hosts hold off on switching PHP versions until PHP 8 tests are passing on core’s TravisCI, stating that “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s TravisCI (it runs the same tests) is already running PHP 8, fortunately, so some things are visible there.”

Per @javiercasares‘ recommendation, two issues were created to check the phpunit-test-reporter and phpunit-test-runner for PHP 8 compatibility to make sure the tools are ready.

@francina investigated the potential for implementing a similar approach to what was taken for PHP 7.4, and mentioned “The test runner could start including PHP8  + ..definitely open tickets in tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. to highlight new and deprecated things in PHP8 that need fixing in WP.”

PHP 8 related tickets are being tracked with the php8 keyword, and help is welcome — both with existing tickets, and new ones!


@javiercasares said they are planning to check pull requests in the team’s GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. repos today (a review/report of the issues is now posted here).

@mikeschroder did a little handbook change review this week, and hopes to do more this week. Also committed the change to invalidate opcode cache on update in core, and has requested testing.

Next Meeting

The next meetings will be in the #hosting-community channel on July 08, 2020 at 09:00 UTC and July 08, 2020 at 18:00 UTC

Hope to see you then!

#hosting-community, #meetings