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

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

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

Hosting Meeting Notes: February 15, 2017

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

Promoting WordCamps

  • @calebb’s post went live on Friday.
    • https://make.wordpress.org/hosting/2017/02/10/building-a-machine-readable-list-of-wordpress-events/
  • @samuelsidler dropped in to encourage us to loop in #meta and #marketing on future efforts.

Distributed Unit Testing

“Best Practices” Documentation

  • @aaroncampbell quickly reviewed @voldemortensen‘s “Call for Documentation” post and published it during the meeting.
    • https://make.wordpress.org/hosting/2017/02/15/call-for-best-practices-documentation/

Community Summit

  • Work still needs to be done on the “Call for Topics” post.
    • @mikeschroder and @boogah committed to getting something up in last week’s meeting.
    • They’ll try to get something up by the February 22 meeting.
  • Until it gets posted, think about topics you’d like to have discussed at the summit.

Feedback

Couldn’t make it to this meeting? Would you like to lend a hand to one of the initiatives above? Please drop into the comments and share your thoughts!

Next Meeting

The next meeting will be in #hosting-community on Wednesday, February 22, 2017 at 1600 UTC. While that may be early (or late) for a number of you, we’d really love to have you join us.

#notes, #weekly-hosting-chat

Hosting Meeting Notes: February 8, 2017

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

Promoting WordCamps

Distributed Unit Testing

  • @octalmage’s post for Make Hosting collecting thoughts around last week’s conversation needs review.

“Best Practices” Documentation

  • @voldemortensen is in the process of working up a draft for the Make Hosting blog.

Community Summit

Group Description

  • Discussion around the group description for the main make.wordpress.org page.
    • “We work together on hosting best practices and tools for the community.” was the frontrunner.

Feedback

Miss this meeting? Want to pitch in on one of the initiatives above? Please feel free to drop into the comments and share your thoughts.

Next Meeting

Our next meeting will be in #hosting-community on Wednesday, February 15, 2017 at 1600 UTC. If you can fit that into your schedule, we’d love it if you could attend.

#notes, #weekly-hosting-chat

Hosting Meeting Notes: February 1, 2017

Here is the summary of Make Hosting’s third meeting in #hosting-community on Wednesday, February 1, 2017 at 1600 UTC (Slack archive).

Updates

“Best Practices” Documentation

  • Some documentation has been sent in from a few sources.
    • Keep it coming!
  • @voldemortensen will try to get a call for docs up ASAP on the Make Hosting site.

Promoting WordCamps

  • @calebb and @smaffulli are working on documentation outlining the available APIs for the Make Hosting site.
    • Should be posted in the next few days.

Distributed Unit Tests

  • This project is still in need of a lead.
    • You’d chat with folks interested in working on the various parts to organize. Everyone will pitch in, but this needs a champion if we’re going to move forward.
    • C’mon, people… Doesn’t anybody want to do this?
  • Update from @octalmage re: defining a method for reporting back to .org.
    • Looked into using a pre-built tool (Jenkins, gocd) but both required custom plugins.
    • Those tools are built to grab results vs. having the reports submitted and have good integration with tools like Trac and GitHub.
    • Building something on our own would be a huge task.
  • The OpenStack project has a system with similar scope (RefStack) but it might be too hard to generalize.
    • The approach is that a client runs the tests, gets an XML output and feeds that into the RefStack server. (Example test results)
  • The tests need to be run on the exact server setup that users are going to be on.
    • This way, things like the ImageMagick issue that recently affected a few hosts will be caught early.
  • There was a long discussion around potential methods that could be used.
    • @octalmage agreed to collect the thoughts around this conversation for a future Make Hosting post.

Security

Feedback

Miss this meeting? Want to pitch in on one of the initiatives above? Please feel free to drop into the comments and share your thoughts.

Next Meeting

Our next meeting will be in #hosting-community on Wednesday, February 8, 2017 at 1600 UTC. If you can make that work with your schedule, we’d love to have you. Hope to see even more of you next week! 😃

#notes, #weekly-hosting-chat

Hosting Meeting Notes: January 25, 2017

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

Updates

“Best Practices” Documentation

The current idea is to build a public handbook of the best practices that are generally used in hosting. This could be a variety of topics (and doesn’t need to be a single team).

  • Will probably include things like:
    • Server configuration requirements.
    • Recommendations.
    • Common scaling configurations.
    • Deployment.
  • Need reps from each host that wants to participate to send a sanitized copy of the following information to @voldemortensen (contact on Slack for E-Mail address if needed):
    • Default php.ini.
    • Default nginx, Varnish, httpd configs.
    • What modules you include with PHP.
    • PHP versions offered
    • Any changes you make to default wp-config.php.
    • Any mu-plugins you include and their purpose.
  • Data will be aggregated so it can be grokked and discussion can happen around the differences.
    • There’ll be a Make Hosting blog post on the aggregated data.
  • It was pointed out that some hosts might not want to share all of the above. Whatever they would like to share is welcome.
  • Request for additional volunteers.

Promoting WordCamps

  • WordCamps have an official list available, with a simple API call.
    • Returns JSON with all approved events.
  • Meetup.com has an API.
    • All WordPress meetups are in one single, easy to identify spot.
  • PoC code pulling from WordPress.org and Meetup.com.
    • https://github.com/squidboylan/wordpress-meetup-scraper
    • Builds a combined JSON containing events from both.
      • Easy to filter out recent events only, or by proximity.
  • To start, we need a post/page that details what information the current APIs offer, and how to reach them.
    • Where are these URLs?
    • What is returned in the JSON?
    • Link existing PoC tools.
    • @smaffulli is down to do this.
  • Scope is narrow enough that no additional people appear to be needed at this time.

Security Discussion

WordPress Security Czar @aaroncampbell wants to make sure the WordPress Security Team and hosts work together as much as possible.

  • WordPress has a security notifications list.
    • It’s only for established hosting companies.
    • It’s meant to give you a day or two to prepare for any security issues before a security release.
  • Also trying out a channel meant for hosts to be able to discuss security issues, potential fixes, etc.
  • Private message @aaroncampbell for more information on list and/or channel.
    • He’ll give a primer on what is expected/needed from you, what can’t be shared, etc.

Distributed Unit Tests

The idea is to end up with a common framework for hosts running WordPress tests on their platforms. Also, we’re looking to send reports on tests back to .org. This will allow for more complete testing on actual deployments.

  • @jorbin has some posts about it, with some scoping here:
    • https://daily.jorb.in/2016/05/31/wordpress-automated-testing-next-gen/
  • @danielbachhuber shared some tools he worked on for Pantheon in last week’s meeting notes:
    • https://make.wordpress.org/hosting/2017/01/18/hosting-meeting-notes-january-18-2017/#comment-10
  • The current biggest need is to have someone lead the cause.
    • The project can’t get started without someone to steer the ship.
      • It doesn’t need to be a host that coordinates it.
        • It’s helpful if someone who at least hosts their own installs.
        • At the very least they should have a testbed for the necessary parts.
    • @mikehansenme, @mikeschroder, @joshkoenig, and @octalmage are willing to champion this at their respective hosts.
    • @octalmage kindly offered to look into defining the method for reporting back to .org.

Feedback

Miss this meeting? Want to pitch in on one of the initiatives above? Please feel free to drop into the comments and share your thoughts.

Next Meeting

Our next meeting will be in #hosting-community on Wednesday, February 1, 2017 at 1600 UTC. If you can fit that into your schedule, great! We’d love it if you could attend. Hope to see even more of you next week! 😃

#notes, #weekly-hosting-chat

Hosting Meeting Notes: January 18, 2017

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

Purpose

  • Kicking things off by restating the purpose of the group.

Ideas

  • Hosts should band together and work through things that the core group can never do.
    • Come up with solutions for things like:
      • Upgrading PHP for non-managed users.
      • How we can all generally make WordPress feel and work better for everyone.
      • If core needs PHP module X, can we get enough of us on the same page for core to rely on that?
  • Best practices documentation (see: WordPress Hosting Handbook).
    • Server setups are going to vary, but there are definitely best practices that we can document.
      • Who puts default settings in wp-config.php?
      • System plugins.
      • Standard “default” php.ini values.
        • Hosts should offer feedback on things like upping default memory limits in core. (#29341)
      • Scaling and performance optimizations.
        • The REST API and plugins like WooCommerce are changing how people use WordPress.
  • Promoting and encouraging WordCamp attendance.
    • Hosts are uniquely positioned to promote regional WordCamps to customers.
      • WordPress has great brand awareness amongst customers.
      • WordCamp? Not so much.
      • Knowledge sharing “in your own backyard” is a big draw for some people.
    • Can leverage geographical customer data to promote upcoming local camps.
      • “As a WordPress user, here’s an event near you that you might find educational and informative that you didn’t even know was a thing!”
    • May require support from the #community-events team to help automate it.
      • An API would make it easy to tie into.
  • Making sure new features are scalable on implementations of all sizes.

Assignments

Feedback

Miss the meeting? Interested in helping on one of the initiatives above? Please feel free to drop into the comments and weigh in.

Next Meeting

Our next meeting will be in #hosting-community on Wednesday, January 25, 2017 at 1600 UTC. If that works with your schedule, we’d love it if you could attend. Hope to see more of you next week!

#notes, #weekly-hosting-chat