Hosting Meeting Notes: July 31, 2019

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

Here is the agenda from the meeting.

Attendees: @jadonn @brettface @chanthaboune @aaroncampbell @dhsean @clorith @antpd

Housekeeping

A follow-up post in response to the PHP extension discussion is pending!

Volunteers are welcome! If you are interested in helping with blog posts, meeting notes or in being more involved in the hosting community team in general, please reach out to @jadonn@mike, or @amy kamala to get started!

Thank you @aaroncampbell for volunteering to proof read. Much appreciated!

#core – Feedback Requested!

The #core team is looking for feedback on this post: should security fixes continue to be backported to very old versions of WordPress

Also looking for feedback on this proposal to update WordPress versions lower than 4.7 automatically.

Host input is encouraged! Please don’t hesitate to participate in the conversation by replying to the post or bringing it up in the channel discussion!

Hosting Options on WordPress.org/hosting

Host listings on https://wordpress.org/hosting/ are pending review.

@chanthaboune apologized for being unclear about this process at WCEU, and stated the main goal is to “offer hosting options on our /hosting/ pages that take into account localized service.”

As a first step, the matrix used for hosting requirements must be re-visited and refined.

@clorith stated that doing requirement checks in the public arena alleviates liability

@aaroncampbell brought up that allowing public input could flood the /hosting page with an overwhelming amount of host listings.

@brettface would like to see a visual re-vamping of the /hosting page to make it easier to read and more accessible.

@jadonn believes that “having a more transparent process or set of requirements would be beneficial”

@aaroncampbell mentioned that  @remkus at Yoast may have previously helped put together what they use for https://yoast.com/wordpress-hosting/

@chanthaboune would love a copy of this as a starting point and stated that “.. our next steps are to figure out what the requirements to be included are”

Thank you to @antpd who volunteered to collect notes, ideas and information for the next meeting where the discussion will continue.

Other teams to be involved in this project are Marketing, Design, Polyglots and Meta to name some.

Open Floor

@clorith asked that hosts please be aware of the proposal to increase the minimum recommended version of PHP in WordPress

Please feel free to comment on the post!

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

+make.wordpress.org/updates

Hosting Meeting Notes: July 22, 2019

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

Here is the agenda from the meeting.

Attendees: @comunicamuh, @amykamala, @zodiac1978, @danfoster, @mdw1989, @mikeschroder

Housekeeping

There was an update on actions since the suggestions last week to make it clearer when team meetings are scheduled.

The channel topic now links to a listing of the next meetings, that list now shows meetings 30 minutes after they’ve started, and the per-team meeting listings are more discoverable. On “Add to Calendar” functionality, the meta team referred to a ticket about iCal here.

Community

Mentioned that there is a call for volunteers for the Handbook Working Group and feedback for the WordPress user and developer survey, which were topics during last week’s meeting.

Team Feedback / Engagment

@amykamala lead a discussion on ideas to get folks more involved in the team. Topics included:

  • Request for project and/or event recommendations
  • Ideas for making the group more useful for folks
  • Making space for conversation

Open Floor

@zodiac1978 requested an update on the PHP Extension recommendations. This is at the point where feedback needs to be compiled and shared. If you’d like to help put a post together, please leave a comment on this one!

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

+make.wordpress.org/updates

Hosting Meeting Notes: July 17, 2019

Here’s the summary of our meeting in #hosting-community on Wednesday July 17th, 2019 at 1700 UTC (Slack archive).

Here is the agenda from the meeting.

Attendees: @jadonn @brettface @fahimmurshed @amykamala @clorith @antpb

Housekeeping

On Note-Taking

The hosting-community team is looking for volunteers to take meeting notes to help balance out demands.

If you’re interested, please comment on this post, or message @mikeschroder, @jadonn or @amykamala on WordPress Slack. No prior experience or permissions are required and this is a great way to get more involved with the community.

On Meeting Time

A post about meeting times and the impact on having two alternate meeting times will be coming out soon! It’ll be posted to the team blog, and will be mentioned in meetings.

A number of changes were made based on everyones’ feedback about the visibility of meeting times:
• The Slack channel topic now has a link to https://make.wordpress.org/meetings/#hosting with the upcoming meeting times posted.
• Meeting times also now stay active on https://make.wordpress.org/meetings/ throughout meeting time.
• The meetings page was changed to allow filtering for meetings for specifics team and links were added for “add to my calendar” functionality

Thank you all for all of the suggestions for improving meeting time visibility and helping folks come to team meetings!

PHP Recommendations

PHP Extensions

Thank you to everyone who engaged in the discussion about PHP extensions! The conversation is pending closure, but any additional comments can still be posted in the replies here.

Minimum required PHP version

Thank you everyone who left feedback on the Site Health team’s post about the next minimum required version of PHP! Please feel free to share your thoughts in a comment on this post as the discussion continues. Conclusions of this discussion are coming soon.

Community

WordPress core E2E testing

WordPress Core has added end to end testing! The testing is emulates a human user scenario to identify potential problem areas and validate different flows. Hosts are encouraged to set up E2E testing and any contributions are values! For more information on E2E testing, check out the announcement from Core.

Call for #community-team Volunteers

The #community-team is looking for help reviewing the make.wordpress.org handbook! The goal is to make the handbooks more accessible and easier to use.

Volunteers are asked to dedicate 1-2 hours per week. This project completion date is projected to be in October, prior to WordCamp US.

More information found here.

WordPress User and Developer Survey

The WordPress User and Developer Survey is being updated! Please feel free to provide any feedback and suggestions, as well as find more info here.

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 Monday, July 22, 2019 at 1400 UTC. Hope to see you then!

+make.wordpress.org/updates

Hosting Meeting Notes: July 8, 2019

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

Here is the agenda from the meeting.

Attendees: @clorith, @javiercasares, @danfoster, @aaroncampbell, @mdw1989, @pandjarov, @lightsoutdave, @amykamala, @fahimmurshed, @mikeschroder

Housekeeping

On Note-Taking

It would be great to have a rotating set of folks to take meeting notes so that no one person gets burned out, and so that when folks are away, there’s still someone to take notes for posting here.

If you’re interested, please comment on this post, or send @mike on WordPress Slack a message, and we’ll get a rotation set up! You don’t need any prior experience or permissions for writing on the site; this is a great way to get more involved with the team.

On Meeting Time

@mikeschroder noted that there’s still a post to come on metrics from meeting times. So far, it looks like there are about the same amount of attendees at the meetings, but with additional folks that weren’t able to attend before.

This is great! There has, however, been confusion about when the team is meeting each week.

Folks suggested:

PHP Recommendations

Extensions

Conclusions coming soon from the discussions around PHP extension recommendations. Please add any feedback on this post.

Versions

The Site Health team has requested feedback from the hosting team on how to set the recommendations for Site Health in the future.

There was discussion lead by @clorith on whether/the best way to test how recommending PHP versions affects new version adoption.

@clorith noted that the team would be taking all of the feedback and making a decision on the version bump soon.

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

+make.wordpress.org/updates

Hosting Meeting Notes: June 24th, 2019

Here’s the summary of our meeting in #hosting-community on Monday June 24th, 2019 at 1700 UTC (Slack archive).

Here is the agenda for the meeting.

Attendees: @abdullahramzan @mehul0810 @redituk @JavierCasares @Mike @amykamala

Continued Discussion on Auditing PHP Extensions

An audit of the list of recommend PHP extensions in the Hosting Community handbook has been ongoing. Thanks to all who have participated! Some details being discussed are:

• Should the Hosting Handbook recommend extensions beyond what core requires?
• Should Site Health Check recommend extensions beyond what core requires?
• Where should requirements and recommendations for core be located?
• What changes would you recommend making to the current list?

Contrary to the sentiment during Wednesday’s meeting, the consensus in today’s meeting is that core should provide information on core requirements only, and not extend beyond that. Some points are:

• Providing recommendations can add more work for core developers and may complicate things.

• Plugins and themes can make recommendations for additional extensions if need be.

• Providing the list of required extensions in the handbook is sufficient.

Question: Would it be prudent to put a call out to hosts to provide a list of modules installed in their systems to help determine what extensions can and can not be used?

Trac ticket #47454 was filed in relation to the PHP extensions audit. Feel free to add to the Trac ticket and continue the discussion here:

Hosts are also encouraged to participate in PHP Unit Testing to help assure compatibility and preemptively resolve conflicts and errors:

WordCamp EU and Contributor Day!

WordCamp Europe was on June 20-22 and June 20th was Contributor Day! Thank you to all participants! More info found here

@Mike reported from WCEU that this talk on Security, by @smitka, is worth viewing once available:

WordCamp talks from all over the globe can be seen on https://wordpress.tv/

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, July 3rd, 2019 at 1700 UTC. Hope to see you then!

Hosting Meeting Notes: June 19th, 2019

Here’s the summary of our meeting in #hosting-community on Wednesday June 19th, 2019 at 1700 UTC (Slack archive).

Here is the agenda for the meeting.

Attendees: @jadonn @fahimmurshed @earnjam @francina @amykamala

PHP Extensions Audit Continues

The Hosting Community team has been asked to audit the list of recommend PHP extensions in the Hosting Community handbook. Thank you to everyone who has participated! Some details being discussed are:

• Should the Hosting Handbook recommend extensions beyond what core requires?
• Should Site Health Check recommend extensions beyond what core requires?
• Where should requirements and recommendations for core be located?
• What changes would you recommend making to the current list?

Some hosts mentioned that offering both a list of required extensions as well as recommended ones would be useful, provided that it is made clear what is required and what is not.

Some ideas are:

• Info on PHP extensions could be provided as a phpinfo page under Site Health – > Info in wp-admin.

• An alert in wp-admin could notify users if a required extension is missing.

• List extensions both required and recommended in the handbook for reference.

Trac ticket #47454 was filed in relation to the PHP extensions audit. Feel free to add to the Trac ticket and continue the discussion here:

WCEU and Contributor Day

WordCamp Europe is happening June 20-22! More info found here

June 20th is Contributor Day! Thank you to all participants!

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

PHP Requirements Check-in

Hey everyone!

There’s been some conversation around the PHP extension requirements and recommendations posted by the hosting team following the release of WordPress 5.2 and Site Health Check.

I’m super excited that folks are digging into this documentation to ensure the recommendations are the best they can be for WordPress users!

This post is meant to introduce the background of the list and gain further feedback on the best way forward.

Background

There wasn’t an official set of PHP extension requirements from the WordPress project at all, and the hosting team decided to create documentation so that this would be more clear for both users and hosts. The team hoped this documentation could eventually be used to update the official requirements, since they are not currently complete.

The team did an initial pass with various contributors, including an audit of core to find references to extensions.

This page on the handbook was the result of those folks’ work, and was used as a reference during the addition of Site Health Check in 5.2.

Site Health Check both lists strict requirements and makes recommendations when extensions aren’t strictly required, but WordPress works better with those extensions present.

Feedback

Following the release, there have been tickets about changing the Site Health Check requirements and recommendations, and #47454 is the trac ticket where the most recent conversation has been happening.

Following that ticket, there was some chat in #hosting-community, and @dd32 did a first pass on the requirements based on his knowledge of the code base (thanks!). He also gave the idea of using an automated checker to get more detail on requirements. There’s also been some conversation about them in the two hosting meetings since.

There are varying opinions on what should be in Site Health Check, including whether it should be only what Core requires and uses, or whether it should include some things that are helpful to users, but are not absolutely necessary for WordPress to have all of its functionality.

I’m also interested if the Hosting Team Handbook is the best source-of-truth for these requirements and recommendations to be, since the requirements are defined by core itself.

Do you have any thoughts on the above? Please leave comments on this post!

Interested in feedback in general, but as a bit of recap, here are a few conversation points to start things off:

  1. Should the Hosting Handbook recommend extensions beyond what core requires?
  2. Should Site Health Check recommend extensions beyond what core requires?
  3. Where should requirements and recommendations for core be located?
  4. What changes would you recommend making to the current list?

Thanks everyone — looking forward to the discussion!

+make.wordpress.org/core

Hosting Meeting Notes: June 5th, 2019

Here’s the summary of our meeting in #hosting-community on Wednesday June 5th, 2019 at 1700 UTC (Slack archive).

Here is the agenda for the meeting.

Attendees: @jadonn @fahimmurshed @supersoju @ugyen @emaildano @kamala @rahuldsarker @pandjarov

Housekeeping

Team Leadership

We are still looking for people to help with taking notes and leading meetings. If you are interested in helping out, please feel free to comment on this post! Helping with meetings is a great way to start contributing to the team.

Thank you @kamala and @emaildano for volunteering to help out with team organization and notes!

Anyone else interested in learning more about being a team representative should also consult @chanthaboune’s post about team lead interest for more information and links to helpful resources.

Meeting Time Change

We mentioned again @mikeschroder’s team blog post about the meeting times change. If you have any thoughts or feedback about the alternating meeting times, the best way to share it is leaving a comment on that post.

PHP Extensions Audit

The Hosting Community team has been asked to audit the list of recommend PHP extensions in the Hosting Community handbook. It appears this list is no longer up to date and no longer accurately reflects the true requirements of WordPress.

Trac ticket 47454 was filed in relation to this question. The extension list was referenced when making the Site Health tool. Inaccuracies in the extension list are driving inaccuracies in Site Health it seems.

@jadonn will write a post on this topic for a place to provide feedback and have further discussion among the team.

PHP Statistics

@dd32 asked for feedback about how useful a centralized collection of anonymized PHP usage statistics would be for hosts. The general consensus seemed to be that such information would be valuable.

Some of this information, such as PHP versions and extensions in use, is currently being captured by hosting companies who participate in the WordPress PHP Unit Testing program the Hosting Community team supports.

@supersoju asked for information about how to best run and report data for multiple products or hosting environments. @earnjam suggested that feedback should be submitted to either the GitHub repo for the PHP Unit Test Runner or to the GitHub repo for the PHP Unit Test Reporter.

@dd32 did provide more information after the meeting. @dd32 did caution that this project is still just an idea at this stage. In addition, although hosts running the tests is useful, @dd32 pointed out there’s a significant long-tail of hosts with less than optimal PHP setups. Collecting PHP version and extension information in general would help the WordPress project capture information about these other hosts.

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 Monday, June 10th, 2019 at 1400 UTC. Hope to see you then!

Hosting Meeting Notes: May 27, 2019

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

Here is the agenda for the meeting.

Attendees: @mikeschroder @mazeheld @amykamala @Pandjarov @asa

Housekeeping – Meeting Time Check-In

Please share feedback and ideas on the new meeting times here:

WordPress 5.2

DreamHost noted a conflict with cron events and memcached (possibly other object caches) where cron jobs get stuck in cache and do not execute with WordPress 5.1 and up. Folks present didn’t know of an existing trac ticket.

Open Discussion

Plugin Security Checks

@Pandjarov proposed the idea of doing a thorough review of the existing plugin repo to identify security holes and other security concerns, on an ongoing basis. Potentially establishing checks to scan for potential security risks in code as commits are made. The idea of a security check/scanner integrated into WordPress Core was also brought up. More discussion pending.

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

Hosting Meeting Agenda – May 27, 2019

Hi everyone!

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

Here’s what I have so far:

  • Housekeeping
    • Reminder to provide feedback on how meeting times are working
  • WordPress 5.2.1
    • Check-in: How’s the new version going?
  • 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