Test Runner and Reporter Multiple Submissions Project
The hosting team is starting a GitHub project geared towards making improvements and updates to the phpunit test runner and reporter. The project is kicking off with a feature request for the runner and reporter to facilitate multiple result submissions per host. The project is in its research phase and anyone who wishes to get involved is welcome to!
Thank you to Jetpack and WooCommerce as well for your global sponsorship! More details on this years sponsors can be found here while more detailed information on Global Community Sponsorship is available here.
@hristo-sg mentioned that the Global Community Sponsors for 2020 have been forwarded to their events and sponsorship team for consideration!
WordCamp Phoenix is this weekend on the 7th and 8th! Lots of folks were out today in the 1800 meeting while traveling to WCPHX! There’s going to be a contributor day, but not a hosting table this year. Last year brought in over 600 attendees and this year is expected to be just as amazing!
WordCamp Asia is in the end of February! There is going to be a ‘Get Involved’ table at Contributor day. More info found here.
@mikeschroder stated that he’s going to be helping lead contributor day with the hosting team and is looking forward to working with everyone!
@crixu volunteered to take on Runner Issue 91 regarding adding Travis documentation to the handbook. @crixu also mentioned that he’s researching ways to best support the test runner on internal systems to enable partners to contribute with more ease in the future.
@mikeschroder suggested building in some example test scripts for the test runner in hosting and test documentation, as well. Runner Issue 102 was created to follow up on that idea.
- Release Model Working Group
- 5.4 Schedule
- E2E Testing: 3 Recent Test Reporter additions -- Thanks!
- WordCamp EU: Leave no contributor behind
- What did y'all work on last week? Plans to work on this week?
## Open Floor
Release Model Working Group
A Release Model Working Group is being formed and had its first meeting on January 29th. The working group is aimed to help streamline the release process, taking into consideration the ambitious release schedule set for 2020. More details on the working group found here.
WordPress 5.4 Schedule
The WordPress 5.4 development cycle is underway with the first Beta version geared for release in February!
E2E Testing – Recent Test Reporter Additions
There were 3 new test runner submissions put in recently! Thank you to everyone who contributes to testing!
Testing helps keep WordPress informed on common issues that hosts encounter, which supports the improvement process.
We discussed about naming the meetings according to its target audiences. Current ideas are:
AM and PM Meeting
APAC/EMEA and EM/AM Meeting
Feel free to comment on what names you prefer in the comment section.
@mikeschroder left some comments on the test runner and places to contribute here: https://wordpress.slack.com/archives/C3D6T7F8Q/p1579075230111800 Started some edits on pages in the Hosting team site. Most obvious is the header, where I added a list of potential places to contribute.
@mikeschroder also started to do some edits to the hosting team sites. Most obvious is the header, where he added a list of potential places to contribute.
@gtaniguchi raised again the importance to have multiple environments under 1 account for the php-unit-tests. Additionally, @gtaniguchi raised also the question regarding the need for nodeJS, grunt and so on for the tests as these tools couldn’t be installed on some environments and the WordPress Core don’t need them. @mikeschroder clarified that these tools are needed in the preparation environment and not the final testing environment. They set up a separate VPS that connects to the testing environment via SSH as the tools are needed to prepare the testing environment. Another option suggested by @mikeschroder would be to skip the building of WordPress each time the test is done. If such a feature is wished someone should open an issue for this on github.
@Crixu asked for the attendees of the contributor day on the upcoming WordCamp Asia 2020. Of the participants, @mikeschroder will join so far.
@Crixu brought up an issue with some servers located in China which returned an HTTP-Code 429 while trying to get the latest package from wordpress.org. Leave a comment if you encountered a similar issue.
@mikeschroder asked if folks would find official versions of the handbook in other languages useful.
@mazeheld mentioned working on an article on “how to run multiple instances of the unit tests on several setups for hosts”, also bringing up that “unless you register a different user for every env only the last run test result will be listed on the make.wordpress.org host test results”. @mikeschroderopened an issue for this.
This meeting was the last hosting team meeting of 2019! Thank you to everyone who has contributed and participated this past year! Meetings will reconvene on Wednesday January 8th, 2020! Happy Holidays!
Meeting Time Changes
Over the past few weeks team members have provided feedback in a survey regarding Meetings days and times. Thank you to everyone who participated! Based on survey results, the overwhelming majority are in favor of both meetings occurring every week on Wednesdays at 0900 and 1800 UTC, instead of the current alternating schedule.
Starting January 6, 2020, Hosting meeting days and times are changing. Both team meetings will be on Wednesdays every week, at 0900 UTC and 1800 UTC.Please note, there will be no more meetings on Mondays, moving forward.
Both meetings will share an agenda, and possibly share meeting notes. The hope is that team communication will become more inclusive, engaged and productive.
@jadonn mentioned that it sounds useful, also stating that at the moment there are no projects to track.
@grafruessel stated that the German hosting community has discussed a trello board helping the hosting team become more accessible. In the start of the year the trello board can be more filled out, possibly starting with updating the Handbook.
@jadonn agreed that it’s time to revisit updating the documents, handbook and best practices information to assure those are current. The Hosting team hasn’t worked on it in several months. He asked @grafruessel to put together a simple example board or card for updating the handbook to demonstrate how it can be valuable.
@grafruessel will be starting that next year and may need some help!
@grafruessel and @crixu discussed the phpunit test runner; if it’s possible to make it easier to install, perhaps with a batch script. They will look into it further, and @mike added that the docs and open issues for that test need some work too. Volunteers are welcome to get involved!