Tide Chat Summary: November 19th

This post summarizes the 2-hour Tide active working session from November 19th 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

Next meeting

The next meeting, a 30-minute update/open floor session, will take place on December 3, 2019 at 20: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

Tide Chat Summary: November 5th

This post summarizes the Tide chat meeting from November 5th 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

  • Significant progress at WCUS Contributor Day working through open issues and PRs in the 1.0.0 milestone
  • @valendesigns in offsite meetings all week, aiming to resolve any issues in PRs and get those to merge and a v1.0 RC later this month

Proposal to adjust Tidechat scheduling

  • Proposal from @jeffpaul to adjust Tidechat scheduling to every 2 weeks, alternating between a status update/open floor session and a working session.
  • One week we’d have a regular update meeting / open floor session for 30 minutes, then 2 weeks later we’d have a mini-Contributor Day-like working session for 2 hours (possibly via video-chat with fall-backs to audio-only and text-only as contributors prefer) with folks who show up to work through an issue together (ideally decided upon in the previous tidechat).
  • Part of the reasoning is that our weekly meetings have gotten repetitive in what’s happened since the previous weeks, hoping to give folks an extra week to work on contributions, and also that we tend to see the biggest jump in contributions when we’re working together on a topic.
  • This proposal came out of discussions at WCUS Contributor Day as something worth trying to improve our progress towards v1.0.
  • It would mean that our next tidechat would be on November 19th and would be an active working session. Then December 3rd would be an update/open floor session. And our final tidechat for the year on December 17th would be another working session.
  • Our first meeting in 2020 to be January 7th as an update/open floor where we discuss how this adjusted tidechat schedule has worked and what further tweaks we’d want to make.
  • @valendesigns @kkoppenhaver @williampatton @fahimmurshed concurred with the proposal so we’ll shift to that starting immediately

Open floor

  • Thanks to all everyone who showed up to the Tide table at WCUS Contributor Day this weekend. Your contributions and input are greatly appreciated!

Next meeting

The next meeting, a 2-hour active working session, will take place on November 19, 2019 at 20: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

Tide Chat Summary: October 29th

This post summarizes the Tide chat meeting from October 29th 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

Open floor

  • Plan for WCUS Contributor Day (besides items noted above) is to spend the first hour getting folks on-boarded, working through issues/PRs, and defining our roadmap
  • Second half of Contributor Day, @valendesigns and @jeffpaul will meet with other teams to see how they might integrate/interact with Tide to further inform our roadmap
  • Ideal outcome is deploying a stable Tide v1.0 by the end of the day

Next meeting

The next meeting will take place on November 4, 2019 at 20: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

Tide Chat Summary: October 8th & 15th

This post summarizes the Tide chat meeting from October 8th (agenda, Slack archive) and October 15th (Slack archive) in the #tide Slack channel.

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

Open floor

  • Preparing for WCUS Contributor Day, we now have the Contributor Day label for issues well-suited for that day
  • If you have issues you’ve been waiting to open, then please look to do those here in October so we can consider tagging more for the WCUS Contributor Day to ensure folks who show up have something they can help with on Tide.
  • @valendesigns and @jeffpaul to focus on meeting with other Make teams to see how they can leverage the data in the WP.org UI and how else Tide might help them; then turning that info into a longer term roadmap
  • @kkoppenhaver to help with new contributor onboarding / assisting folks with questions on Contributor Day-labeled issues

Next meeting

The next meeting will take place on October 22, 2019 at 20: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

Tide Chat Summary: September 24th

This post summarizes the Tide chat meeting from September 24th 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

  • 4 new PRs from @pierlo in the milestone (see wptide/wptide and wptide/pkg)
  • @pierlo also working on a PR for wptide#177
  • @dingo_d, automation rep from Theme Review Team, working w/@jrfnl to move the WPThemeReview repo to the WordPress org
  • @dingo_d to start working through issues and writing sniffs for PHPCS, aiming for smaller amounts of false positives; this generally relates to wptide#180
  • @jeffpaul noted to version number the ruleset to help track which version is audited against themes in the Tide API

General announcements / Open floor

  • Next week’s meeting is cancelled due to travels, so we’ll catch up on Tuesday, October 8th
  • Reminder of Tide table at WCUS Contributor Day, please stop by to say hi and help contribute

Next meeting

The next meeting will take place on October 8, 2019 at 20: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

Tide Chat Summary: September 17th

This post summarizes the Tide chat meeting from September 17th 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

General announcements

Next meeting

The next meeting will take place on September 24, 2019 at 20: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

Tide Chat Summary: September 3rd and 10th

This post summarizes the Tide chat meeting from September 3rd in the #tide Slack channel (agenda, Slack archive) and September 10th (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

General announcements

  • WCUS organizing team looking to confirm who will be leading the Tide table, @valendesigns and @jeffpaul will both be there to co-lead, @kkoppenhaver will also be there
  • If you also plan to attend, please let us know so we can coordinate efforts, thanks!
  • We plan to have new contributors run local setup and will have some smaller issues targeted for folks to work on, but please open any other issues with the Contributor Day label that would be good for folks to accomplish within an hour or so

Next meeting

The next meeting will take place on September 17, 2019 at 20: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

Tide Chat Summary: August 20th and 27th

This post summarizes the Tide chat meeting from August 20th in the #tide Slack channel (agenda, Slack archive) as well as August 27th (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

  • Down to 7 issues in the milestone as wptide#184 was closed by pkg#20
  • @valendesigns to redeploy the Kubernetes clusters with the updated images
  • Caching issue and rate limiting are the best places for others looking to contribute, all help is greatly appreciated!
  • @kkoppenhaver to take a look at wptide#178
  • @valendesigns: once PHP 7.4 hits stable release and compat repo ready, we’ll want to add support and tests for PHP 7.4
  • @valendesigns: upgrade of WordPress is blocked by trying to figure out what changed in the REST API in 5.0+ that’s causing breakage
  • @jeffpaul: worth noting that WP 5.3 is due out in November so this update will get continually more complex the longer it takes (and more major releases make it out)

General announcements

  • @clorith: thankful that the Tide APIs for data are very easy to work with, latest Health Check plugin update uses them to provide a plugin compat tool for quick indication of how an upgrade will work out

Next meeting

The next meeting will take place on September 3, 2019 at 20: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

Tide Chat Summary: August 6th and 13th

This post summarizes the Tide chat meeting from August 6th in the #tide Slack channel (agenda, Slack archive) as well as August 13th (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

  • Continue to roll with 8 issues remaining in the milestone
  • @valendesigns to look into adding tests to pkg#19 and then merging that in
  • 2 good first issue items in the milestone, would love a PR on either of those (wptide#178 on an API update and wptide#112 on a caching issue)

General announcements

Next meeting

The next meeting will take place on August 20, 2019 at 20: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

Tide Chat Summary: July 23rd

This post summarizes the Tide chat meeting from July 23rd 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

  • 8 issues in the milestone
  • Looking for help from the community on the caching and rate limit issues
  • Upgrade of WP version would be helpful for someone from the community to figure out what changed in the REST API from 4.9 to 5.0 that is keeping us from upgrading
  • @valendesigns to review pkg#19, test with some audits, and add test coverage
  • Cloud migration to new GCP organization underway, taking GCP support a bit longer than expected but progressing regardless

Next meeting

The next meeting will take place on July 30, 2019 at 20: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.

#hosting-community, #summary, #tide-chat