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

Tide Chat Summary: July 16th

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

  • Back down to 8 issues in the milestone
  • wptide#170 got resolved by wptide#187 and docs#35
  • wptide#100 got punted to Future Release
  • @FahimMurshed unable to install on Windows/Laragon or Ubuntu/XAMPP, will look into shutting down other servers while bringing up the Docker containers to avoid port collision (especially 80 and 3306)

General announcements

  • @valendesigns aiming to migrate the servers this week, will be at Google this week and try to get help in detaching the project on GCP so it can be moved
  • Discussion in #meta about testing the data from Tide ahead of showing it on the .ORG plugin pages, questions about the validity and accuracy of the data as well as what specifically to show on the .ORG pages
  • pkg#19 only remaining item from WCEU that hasn’t gotten to a commit, @valendesigns to review this week and add tests to it

Next meeting

The next meeting will take place on July 23, 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

Tide Chat Summary: July 9th

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

  • We went up from 8 to now 10 issues in the milestone
  • @jeffpaul noted that wptide#170 is done once wptide#34 gets through review/merge, otherwise the Tide profile badge post summarizes most of the changes/updates
  • Awaiting update from @FahimMurshed and @SandyGarrido on their separate progress on testing Windows setup as part of wptide#100; if no further progress this month then we’ll punt to a future release
  • @valendesigns worked with @dd32 to setup the data sync from Tide to .org at WCEU, needs to check about adding data from themes after the data sync is validated (@jeffpaul to check on progress on meta#4309 with the Meta team)

General announcements

Next meeting

The next meeting will take place on July 16, 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

Tide Chat Summary: June 18th

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

General announcements

Next meeting

The next meeting will take place on June 25, 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