Hosting Meeting Notes: April 25th, 2018

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

Attendees:
@mikeschroder @danielbachhuber @andrewtaylor-1 @jadonn @aaroncampbell @josh2k5 @antpb @brettface @desrosj

Team Organization

  • WordPress.org contributor and team badges were given out.
    • Contributor badges are for concrete contributions, such as making a contribution to one of the team’s active projects.
    • Team badges are for team members who show a combination of contributions, participation, and helping with planning and execution of team projects.
    • If you did not receive a badge, and you feel like you should have, please message @mikeschroder on Slack.
  • The Contributor Drive documentation was passed back to community team for inclusion in future contributor drives.
    • Thank you everyone who added to this documentation!

Hosting Best Practices Documentation

Gutenberg

  • @danielbachhuber had three updates
    • Plugin compatibility test results:
      • Plugin compatibility database, announced March 1st, 2018, has had 70 testers who have tested 861 out of 5000 total plugins.
      • Of 861 tested plugins:
        • 219 (25.44%) are compatible.
        • 518 (60.16%) are likely compatible.
        • 25 (2.9%) are likely not compatible.
        • 39 (4.53%) are not compatible.
        • 60 (6.97%) are in “testing” (i.e. someone started a test and did not complete the test)
    • @danielbachhuber would like to focus on acquiring more data, with Try Gutenberg being a big opportunity.
    • @danielbachhuber proposed having the plugin compatibility database be moved into WordPress.org, which would be a large amount of work, but worthwhile if it brings in a lot of useful data.
  • Try Gutenberg is currently scheduled to launch in WordPress 4.9.6, which is scheduled for release on May 15th scheduled to launch in WordPress 4.9.7 as of May 2nd, 2018 (thanks to @aaronrutley for pointing out this was changed).
    • @danielbachhuber asked if team members’ support teams were ready to address Gutenberg support requests
      • @jadonn and @josh2k5 responded they would have to check with their support team for readiness.
      • @jadonn and @josh2k5 asked for official documentation that could be provided to support teams to help prepare support teams
        • @danielbachhuber recommended drawing up an outline of information that their supports teams would like like to have

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, May 2nd, 2018, 1700 UTC. Hope to see you then!