Hosting Meeting Notes: August 30, 2017

Here’s the summary of our meeting in #hosting-community on Wednesday, August 30, 2017 at 1700 UTC (Slack archive).

Distributed Testing

  • @danielbachhuber reported no significant updates on this topic. In particular, no new hosts have been added to the page since last week.
  • @jadonn noted that he’s setting up the test runner on InMotion Hosting.
  • We discussed the procedure for hosts to report issues while running the test runner and for hosts to receive support on those issues. @danielbachhuber suggested, and we agreed, to use the PHPUnit Test Runner GitHub Issues page as a support forum for now to centralize diagnosing issues with the test runner and to help hosts with resolving failing tests.
  • @danielbachhuber recognized @straussd from Pantheon for logging #41716, a bug in the automated database tests. Thank you, David, for reporting the bug!

Hosting Best Practices Documentation

  • @mikeschroder recognized pull requests and contributions that had been made since the last meeting.
  • The documentation is still incomplete. People who want to contribute should submit pull requests with the changes they would like to submit. The best practices repo is open, and both pull requests and reviews are appreciated!

Feedback

Miss this week’s meeting and want to discuss the initiatives above? Spend some time in the comments and share your thoughts!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, September 6, 2017 at 1700 UTC. Hope to see you then!

#best-practices, #documentation, #notes, #testing, #weekly-hosting-chat

Hosting Meeting Notes: August 23, 2017

Here’s the summary of our meeting in #hosting-community on Wednesday, August 23, 2017 at 1700 UTC (Slack archive).

Distributed Testing

  • This became live on make/hosting last week, and there are now two hosts participating.
  • @danielbachhuber notes that we should run a beta program for more hosts to work through process before wide promotion. If you work at a host and are interested in getting the WordPress automated test suite running, please ping @danielbachhuber for more details.
  • The primary concerns are around the process for what to do when a failure occurs — how hosts get notified, and what the process should be for for getting them fixed, so we’ll be working through that during beta.

Hosting Best Practices Documentation

Feedback

Miss this week’s meeting and want to discuss the initiatives above? Spend some time in the comments and share your thoughts!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, August 30, 2017 at 1700 UTC. Hope to see you then!

#best-practices, #documentation, #notes, #testing, #weekly-hosting-chat

Hosting Meeting Notes: August 16, 2017

Here’s the summary of our meeting in #hosting-community on Wednesday, August 16, 2017 at 1700 UTC (Slack archive).

Distributed Testing

  • An initial version of this is live on make/hosting! @danielbachhuber notes that we should try to get a couple more hosts on-boarded before promotion. If you work at a host and are interested in getting the WordPress automated test suite running, please ping @danielbachhuber for more details.

Hosting Best Practices Documentation

  • @andrewtaylor-1, who has been heading things up, is out until September, but the best practices repo is open for pull requests for edits or new sections. Help there is welcomed!

Feedback

Miss this week’s meeting and want to discuss the initiatives above? Spend some time in the comments and share your thoughts!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, August 23, 2017 at 1700 UTC. Hope to see you then!

#best-practices, #documentation, #notes, #testing, #weekly-hosting-chat

Call for Best Practices Documentation

One of the topics that has been largely discussed during #hosting-community meetings is coming up with a list of best practices for hosting companies to follow. Currently, we know that virtually every hosting company has a different server OS, default php.ini values, NGINX/Apache configs, etc. We’re looking to get some of those things aggregated to provide suggested defaults and best practices.

Here is some of the data we are looking for:

  • Any plugins or mu-plugins installed by default
  • Any modifications made to wp-config.php by default
  • PHP versions offered
  • Modules available in each PHP version
  • Default php.ini files
  • Default caching configs (Varnish, Memcache, Redis, etc)
  • Default web server configs (NGINX, Apache, etc)

Of course, we’re aware that some things (i.e. security configurations) may be sensitive. We don’t want those things.

This information will be compared, discussed, and picked apart to determine best practices to follow. Our goal is not to debate which hosting company is better. This should be an objective analysis by involved individuals from many hosting companies and potentially individuals not affiliated with any hosting company.

If you would like to contribute to the formation of WordPress hosting best practices and have information to offer, please contact @voldemortensen on Slack.

#documentation