Sean 7:02 pm on January 31, 2018  

Hosting Meeting Notes: January 17, 2018

Here’s a summary of our meeting in #hosting-community on Wednesday, January 17th, 2018 at 1800 UTC

(Slack archive).

Distributed Testing

  • @danielbachhuber indicated that getting Travis CI to report to the page is in final implementation stages
    • He will continue running the build to verify everything works as expected – details here
  • Analysis of the build failures so far are here
  • Once wpdevbot is submitting results @danielbachhuber is creating a way for it to email that info – details here
  • @andrewtaylor-1 asked – Do you need an email address from existing hosts reporting?
  • @danielbachhuber replied – Each bot user should already have an email address — that's what I'm planning to use.

Hosting Best Practices Documentation

  • @andrewtaylor-1 indicated that comments are still being gone through for the Reliability page but more are still welcome
  • There are placeholder stubs in Security and other topics that could use some help as well

Request for Help!

  • Submit any further feedback about the Reliability page
  • Add to or add feedback to any other topics of the Best Practices Documentation

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!

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

Next Meeting

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

Sean 7:14 pm on January 25, 2018
Tags: hosting-community   

Hosting Meeting Notes: January 10, 2018

Here’s the summary of our meeting in #hosting-community on Wednesday, January 10th, 2018 at 1800 UTC

(Slack archive).

Distributed Testing

  • Cloudways and Human Made are now reporting results! That brings us to 5 hosts reporting results!
  • Has the DU project caught any bugs pre-release yet to anyone's knowledge?
    • As of the meeting, there had been no data analysis yet
    • A bug related to an incorrect dependency with `allowfopenurl` that resulted in a ticket
    • So far all hosts that have set testing up, have found things to correct
      • Usually it’s PHP extensions or configuration that aren't quite compatible with WordPress
      • DreamHost, for example, found issues with Imagick due to a regression that would have been caught if the tests had been running in an automated fashion
      • Goals for the end of Q1:
        • Getting the core Travis CI data into the database so we have it as a point of comparison.
        • Prototyping sending an email to the reporting account if host tests fail and core tests have not
          • Will need some language around "here's what you should do about it"
        • @mikeschroder suggested that getting things fixed will probably be connected to #hosting-community at first, until we have a pattern.
        • There was consensus between folks present that hosts could/should create a Trac ticket when they have information to do so.

Hosting Best Practices Documentation

  • @mikeschroder's commented on the reliability page but they still need to be reviewed
  • Other feedback is still welcome! 
  • Target audience
    • More ops folks contributing to the docs would help, so that we end up with the details they want.
    • A lot of the feedback @mikeschroder gave for the reliability article was that it seemed like it was focused towards an end user, rather than someone operating a site.
    • Looking at other open source project documentation for "good examples".
      • Drupal’s PHP Requirements doc has some good stuff in it, with relation to the extended PHP compatibility docs we’ve been building

Request for Help!

  • Look at the test results page for the phpunit-test-reporter
  • Call for thoughts and feedback on this issue.
  • Help with reviewing the Reliability page of the handbook by providing feedback
  • @andrewtaylor-1 has a side project he would like some collaboration from another host on. Contact him directly for more details
    • Idea is to use automated testing on CircleCI (have visual regression, working to add Lighthouse) to bulk update WordPress sites, run the tests, then if things pass, deploy… 
    • Specifically, this would be running on cron to check updates (core, plugins and themes)

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!

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

Next Meeting

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

Sean 2:18 am on January 9, 2018
Tags: , , , ,   

Hosting Meeting Notes: January 3, 2018

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 core’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, Slack or otherwise) when there’s an environment-specific failure.
    • Minor UX 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 Github 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!

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

Jadon N 7:07 pm on September 5, 2017
Tags: , , , ,   

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

robertpd 4:56 pm on August 30, 2017
Tags: , , , ,   

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

Daniel Bachhuber 4:57 am on August 25, 2017  

Announcing Beta Period for Distributed Host Testing

Just over a year ago, Aaron Jorbin suggested a simple idea:

If WordPress really wants to do quality automated testing, we need to rely on the people hosting sites to test vs their stack. To do that, Core needs to provide an infrastructure that both encourages and enables easy automated testing.

Today, we’re happy to announce the beginning of a beta period for exactly this: a framework for any hosting company to run the WordPress PHPUnit test suite on their infrastructure and report the results back to WordPress.org.

At a high level, this framework is two parts:

  1. The phpunit-test-runner, which prepares the environment, runs the test suite, and reports the results back to WordPress.org.
  2. The phpunit-test-reporter, which receives the results, stores them in the database, and displays them in an accessible manner.

We’d love to see dozens of hosting companies participate in this program. Check out Getting Started for an overview on how you can set it up. Then, stop by the #hosting-community channel in WordPress.org Slack with any questions you might have.

Thanks to DreamHost and WP Engine for volunteering the engineering effort to make this project possible.

Mike Schroder 1:18 am on August 17, 2017
Tags: , , , ,   

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

Ian Dunn 12:08 am on March 23, 2017
Tags: make.wordpress.org/community, p2-xpost   

X-post: Showing upcoming local events in wp-admin

X-post from +make.wordpress.org/community: Showing upcoming local events in wp-admin

Jason Cosper 9:48 pm on March 15, 2017
Tags: community-team, meta, ,   

Hosting Meeting Notes: March 15, 2017

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

Distributed Unit Testing

  • @octalmage wants to have a meeting to discuss the future and direction.
    • An informal discussion happened after the Hosting meeting officially ended (Slack archive).

“Best Practices” Documentation

Promoting WordCamps

  • Chats were had with the folks in #community-team and #meta.
  • There’s code for the events API, but no real documentation.
  • If no API documentation or further information is required, we will assume the project is “complete” and leave implementation to interested hosts.

Feedback

Miss this week’s meeting? Want to discuss one (or more) of 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, March 22, 2017 at 1700 UTC. Hope to see you then!

#notes, #weekly-hosting-chat

Jason Cosper 8:08 pm on March 14, 2017
Tags: ,   

Hosting Meeting Notes: March 8, 2017

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

New Meeting Time

  • Starting with the March 15th meeting, we will be meeting at 1700 UTC. This way, a few people who are working on projects — and are having problems with making the scheduled 1600 UTC time — can attend.

Distributed Unit Testing

Promoting WordCamps

  • No updates this week!

Community Summit 2017

“Best Practices” Documentation

Yoast’s PHP WHIP Package

Feedback

Couldn’t make it to this week’s meeting? Would you like to lend a hand to one of the initiatives above? Head on down to the comments and share your thoughts!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, March 15, 2017 at 1700 UTC. We really hope that the new time gives more of you a chance to jump in and help out!

#notes, #weekly-hosting-chat