Here’s the summary of our meeting in #hosting-community on Wednesday, January 3rd, 2018 at 1800 UTC (Slack archive).

Distributed Testing

• Cloudways is now reporting results! That brings us to 4 hosts reporting results.
• @danielbachhuber indicated it would be a good idea to create a game plan on what we would like to have accomplished by the end of Q1
• @mikeschroder suggested a few long term goals for Distributed Testing:
  • Have more hosts represented
  • Report information back to hosts when failures occur that are not also failing on WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s Travis CI.
  • Expose that information to committers so that they know if they’ve broken things on hosts when it’s passing on WordPress core’s Travis CI.
• @danielbachhuber indicated it would make sense to do a 2-4 week dev sprint at some point to cover the following:
  • Research to determine whether an environment-specific failure has happened yet.
  • Writing WordPress core’s Travis CI results to the database, so the system can determine environment-specific failures.
    • @danielbachhuber indicated that this item seems like a low-hanging fruit that he could start with over the next week or so.
  • Sending notifications (email, SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. or otherwise) when there’s an environment-specific failure.
  • Minor UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. improvements to the reporting page (display all reporters at the top, etc.)

Hosting Best Practices Documentation

• @andrewtaylor-1 made the hosting environment page live in the hosting handbook
• @andrewtaylor-1 said it would be better to finish the sections that are closest to being done before exploring auto-publishing from 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. https://github.com/ to the hosting handbook
  • Reliability is the closest to being done
    • Final review to be done by next meeting
      • @andrewtaylor-1 will look for comments from @jadonn and @mikeschroder, as well as any others willing to help out, then he will do a final review for publish after the next hosting meeting.
  • Security has placeholders and needs content for User Accounts, Uploads vs. Core Files, and WordPress Users and Roles
  • Performance has the most placeholders

Request for Help!

• @danielbachhuber would love some help looking at the test results page for the phpunit-test-reporter and offer suggestions for improvements. Suggestions/issues can be added here: phpunit-test-reporter/issues.
• Please help review the Reliability Section and help fill placeholder sections that remain in the 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!

Have questions on how you can help? Join #hosting-community and feel free to ask at any time.

Next Meeting

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

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