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

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

WordPress Community Summit 2017

As mentioned in weekly meetings, the WordPress Community Summit is coming up, and our team has some decisions to make!

The summit organizers have asked for the following by the end of next week:

  1. A list of topics/issues that are relevant for the progress of the team and the WordPress open source project as a whole, prioritizing topics or tasks which are sensitive enough to require in-person discussion.
  2. A list of representatives to attend the Community Summit (this will be based primarily on the topics or tasks).
  3. One or two contributors who are willing to help with the organization of the event.

If you have any suggestions for topics or tasks that would benefit from in-person discussion, or are interested in helping out with organizing the event, please comment below or ping myself or @boogah directly so we can put a list together.

There is also a post with a survey to apply to attend and submit questions if you’re more comfortable with that route.

Thanks!

#community-summit

Hosting Meeting Agenda: February 22, 2017

Here’s the agenda for our next meeting on Wednesday, February 22, 2017 at 1600 UTC in #hosting-community on Slack:

If you have items to add to the agenda — or specific comments related to the outline above — please leave a comment. Looking forward to seeing everyone virtually! 😀

#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

Dive Into Distributed Unit Tests

Recently, I have spent some time looking into using pre-built tools for distributed unit tests. What I found was that all of them were built to fetch the test results. What we need, for this project, is to have the results sent to us. At this point it seems like a custom WordPress solution will be the best route.

There was some discussion in #hosting-community about how the tests would be triggered. Some hosts have scripts that run nightly, so slipping tests into that process would make implementation easy. However, using a nightly solution would make it more difficult to determine exactly which commit caused an issue.

If we move forward with running tests on a per-commit basis, do hosts watch for commits and then report the results? Or do we ping hosts? It seems like pinging hosts would be ideal, but it might not be an option for all hosts. It would be really nice to get some feedback here, so your thoughts would be appreciated.

The first step is to start on the method used to report results. This will be a WordPress based application, with a REST API. Hosts will submit the results with the commit SHA to be aggregated. I’m going to dig into this over the next several weeks and will share a GitHub link when I have something up and running.

Call for Best Practices Documentation

One of the topics that has been largely discussed during #hosting-community meetings is coming up with a list of best practices for hosting companies to follow. Currently, we know that virtually every hosting company has a different server OS, default php.ini values, NGINX/Apache configs, etc. We’re looking to get some of those things aggregated to provide suggested defaults and best practices.

Here is some of the data we are looking for:

  • Any plugins or mu-plugins installed by default
  • Any modifications made to wp-config.php by default
  • PHP versions offered
  • Modules available in each PHP version
  • Default php.ini files
  • Default caching configs (Varnish, Memcache, Redis, etc)
  • Default web server configs (NGINX, Apache, etc)

Of course, we’re aware that some things (i.e. security configurations) may be sensitive. We don’t want those things.

This information will be compared, discussed, and picked apart to determine best practices to follow. Our goal is not to debate which hosting company is better. This should be an objective analysis by involved individuals from many hosting companies and potentially individuals not affiliated with any hosting company.

If you would like to contribute to the formation of WordPress hosting best practices and have information to offer, please contact @voldemortensen on Slack.

#documentation

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