This post summarizes the 30-minute Tide status update and open floor discussion from March 3rd in the #tide Slack channel (agenda, Slack archive).

Reminder that the current Tide focus is integrating PHP Compatibility data from Tide into WordPress.org.  Once PHP Compatibility is integrated into WordPress.org, we’ll assess the next focus to provide the biggest impact to the community.

1.0.0

• @kkoppenhaver making progress on caching issue, working on a proof of concept to ensure code fires when it’s put in the proper place, aiming for an update in our meeting in 2 weeks
• @derekherman been sidetracked on other work, reviewed PR for upgrading WP and things are working just need to merge and deploy to GCP, aiming for resolving that by our next meeting
• @pierlo been sidetracked on work, will attempt to look into Redis caching issue by our next meeting
• @jeffpaul digging into docs site, opened three issues recently with docs#41 likely being most important to consider as it relates to bumping docpress versions

Next meeting

The next meeting, a 2-hour active working session, will take place on March 17, 2020 at 19:00 UTC in the #tide Slack channel.  Please feel free to drop in with any updates or questions.  If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#summary, #tide-chat

This post summarizes the 2-hour Tide active working session from February 18th in the #tide Slack channel (agenda, Slack archive).

Reminder that the current Tide focus is integrating PHP Compatibility data from Tide into WordPress.org.  Once PHP Compatibility is integrated into WordPress.org, we’ll assess the next focus to provide the biggest impact to the community.

1.0.0

• Awaiting @derekherman to merge and deploy wptide#198 to complete the WP 5.3.1 updates across the stack
• No blockers present on wptide#199, should be good to merge after @derekherman gets through wptide#198
• @jeffpaul reviewed and merged wptide#201, wp-tide-api#31, and docs#36 to update some typos/URL strings
• Awaiting @kkoppenhaver to wrap up wporg-tide-api#6 to resolve wptide#186
• @pierlo to add research notes to wptide#112
• Help wanted on wptide#178, please ping @jeffpaul if you’re interested and available!
• We also are on the lookout for folks who can help test our set up instructions and call out areas for improvement, especially folks available to help better document Windows instructions
• @jeffpaul opened docs#39, docs#40, and docs#41 as part of research into improving our documentation website on wptide.org; each could use review/input from those knowledgeable on docpress

Next meeting

The next meeting, a 30-minute update/open floor session, will take place on March 3, 2020 at 19:00 UTC in the #tide Slack channel.  Please feel free to drop in with any updates or questions.  If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#summary, #tide-chat

This post summarizes the 2-hour Tide active working session from January 21st in the #tide Slack channel (agenda, Slack archive).

Reminder that the current Tide focus is integrating PHP Compatibility data from Tide into WordPress.org.  Once PHP Compatibility is integrated into WordPress.org, we’ll assess the next focus to provide the biggest impact to the community.

1.0.0

• @derekherman to test and merge wptide#198
• @pierlo to review wporg-tide-api#6
• Research notes added to wptide#178, tagged @kkoppenhaver on that in hopes he can help triage
• @derekherman to review wptide#199, @pierlo to continue iterating and wrap up work on it as well
• Discussion on docs site and that setup is not ideal, but it’s a low priority to resolve those and will let it ride until after we ship Tide v1.0.0
• @jeffpaul reviewed docs#36, added update to related markdown file, otherwise looks good to merge
• @jeffpaul reviewed docs#37, but not certain we’re following WPCS for docs files so that PR may be dismissable

Next meeting

Schedule conflicts with the meeting time have led us to move the meeting time an hour earlier, so please update any local calendar events you have to account for the new meeting time of 19:00 UTC on Tuesdays.

The next meeting, a 30-minute update/open floor session, will take place on Feburary 4, 2020 at 19:00 UTC in the #tide Slack channel.  Please feel free to drop in with any updates or questions.  If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#summary, #tide-chat