Hosting Meeting Notes: April 18th, 2018

Here’s the summary of our meeting in #hosting-community on Wednesday, April 18th, 2018 at 1700 UTC (Slack archive).

Attendees:
@mikeschroder @danielbachhuber @andrewtaylor-1 @jadonn @harryjackson1221 @josh2k5 @pdclark @t-rave @dws122

Team Organization

  • @mikeschroder announced that @jadonn is helping with team representative work on a trial basis.
  • @jadonn suggested the team look at improving team organization in the future.
    • Specific suggestions were maintaining lists of tasks contributors can do and considering agenda-based meetings.
    • @danielbachhuber suggested the team for now might get better contributions by focusing on currently ongoing projects.
      • @jadonn agreed focusing on current projects now would be good use of time.
  • @mikeschroder asked for input on contributor badges and team badges for the #hosting-community team.
    • @mikeschroder proposed giving a contributor badge to people who make a discrete contribution to the team.
    • @mikeschroder asked for input on what to do for giving out team badges.
      • @jadonn suggested looking at different criteria like number of contributions or contributions and attendance.
    • @josh2k5 and @mikeschroder liked looking at contribution and attendance.
      • Especially, as @josh2k5 suggested, active participation in planning and execution for projects.
    • @pdclark thought they were good metrics to consider and that badges would be a good incentive for contributors.
    • @jadonn mentioned attendance would have to be tracked.
      • @josh2k5 felt that it would be self-evident who should receive team badges as time went on.
      • @jadonn and @mikeschroder discussed how to award badges (i.e. give them out or have people request them).
        • @mikeschroder thought, and @jadonn agreed, that team representatives giving out badges would be better recognition.

Hosting Best Practices Documentation

Gutenberg

  • @danielbachhuber, @jadonn, and @pdclark reported on the Try Gutenberg and Gutenberg plugin compatibility efforts.
    • @danielbachhuber mentioned he would be meeting with a representative from the Gutenberg team to work on a plan for collaboration.
    • @jadonn did some more research into automated plugin testing and has been in communication with the #marketing team about help with outreach.
    • @pdclark made a draft for a related Try Gutenberg ticket and sent it to @danielbachhuber
    • @danielbachhuber was going to review the existing database of plugin compatibility for any useful information.
    • @danielbachhuber was going to work on a first draft of a guide for the integration points for the classic WordPress editor and for Gutenberg.
      • Work is tracked on GitHub here.
      • @jadonn had previously written up a list of this kind of information for the automated plugin work. He will add it to the GitHub issue.

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, April 25th, 2018, 1700 UTC. Hope to see you then!

Hosting Meeting Notes: March 28, 2018

Here’s a summary of our meeting in #hosting-community on Wednesday, March 28, 2018, 1:00 PM CST

(Slack archive).

Contribution Documentation

  • @mikeschroder mentioned that Angela Jin is helping document contributor groups and drives, including info on how to contribute and projects available for contribution. An open call was made for Hosting Community contributors to help write up and proof documentation. @antpb and @ataylorme expressed interest in helping proof and write up info. If anyone else would like to help on this front, please ping @mikeschroder on slack.
  • Two initiatives need attention — @danielbachhuber’s Gutenberg testing, and Hosting Best Practice docs, which @ataylorme has been leading. They’re both in need of significant help.
  • In the last meeting folks mentioned that it might be a good idea to pick a day or days to work together on docs, because pre-scheduled time might help. It was determined that Friday 4/6 at 1700 UTC we will meet to discuss documentation. Please come join us! When the event starts, instructions will be posted in the channel for optionally joining a hangout while working.

Hosting Community Discussion

  • @mikeschroder expressed a need to bring in more representatives for the Hosting Community group. There is open call for nominations (self or otherwise) to help the group with things like organizing meetings, notes, or getting things together for camps and contributor days.

Gutenberg Testing

  • @jadonn mentioned the need for Gutenberg Testing outreach and @miker has joined the group to help in those efforts (Welcome!). A resource was shared by @pdclark on Gutenberg testing: https://github.com/danielbachhuber/gutenberg-plugin-compatibility/issues/4
  • The signup process in the testing site was mentioned to be a bit of a hassle/blocker in contributions to testing. Some discussion was had around sharing authentication via WordPress.org users. @danielbachhuber mentioned that considering things like automation the level of effort to link the two may be overkill. 
  • @danielbachhuber mentioned that we don't take ownership of updating the plugins ourselves, but instead focus on making the compatibility data available/accurate, and then assist the plugin author with guidance on how to make their plugin Gutenberg compatible. Our main focus is just getting data around what is/isn't compatible. 
  • On the topic of automation @danielbachuber warned "The challenge with the existing implementation is that some plugins require configuration before they expose editor UI. Simply taking screenshots of a fresh WordPress install with the plugin activated in some automated manner isn't sufficient. However, if a hosting company were open to it, we could grab customer databases with the plugins already activated, spin them up in some isolated environment, and do our screenshot analysis."
  • @danielbachuber also mentioned "We could potentially generate a ton of plugin incompatibility data by screening the WordPress.org support forums"
  • @danielbachuber also shared a comment that outlines some great steps for testing compatibility: https://github.com/WordPress/gutenberg/issues/4072#issuecomment-356136576

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, April 4, 2018, 1:00 PM CST. Hope to see you then!

#hosting-community#weekly-hosting-chat

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!

#hosting-community, #weekly-hosting-chat

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!

#weekly-hosting-chat

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

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

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.

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

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

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