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 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!

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

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 forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. https://en.forums.wordpress.com/. 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 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 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 pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @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 pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @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 APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. 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 PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.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 loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. in #meta and #marketing on future efforts.

Distributed Unit Testing

  • @octalmage‘s post still needs review.
    • @boogah will work on getting it edited and approved by Friday.
  • @octalmage is ideating on REST endpoints and Swagger style documentation.
    • Will get code up on 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/ soon so he can get feedback.
  • @voldemortensen is planning on writing Pub/Sub functionality to scrape the output of PHPUnit.

“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

  • We need to come up with some folks who will represent the group at the summit at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe in Paris on June 13 & 14.
  • Think about topics that are important to discuss.
  • @mikeschroder or @boogah will make a post about it soon.

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 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. and 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/.
    • 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

  • @aaroncampbell posted a disclosure of an additional fix in 4.7.x regarding an Unauthenticated Privilege Escalation Vulnerability in a REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. Endpoint.

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 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/. for E-Mail address if needed):
    • Default php.ini.
    • Default nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/., Varnish, httpd configs.
    • What modules you include with PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.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 APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. call.
    • Returns JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. 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.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and Meetup.com.
    • https://github.com/squidboylan/wordpress-meetup-scraper
    • Builds a combined JSON containing events from both.
      • Easy to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. 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 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software..
  • 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