Tide Chat Summary: March 31st

This post summarizes the 30-minute Tide status update and open floor discussion from March 31st 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 2-hour active working session, will take place on April 14, 2020 at 18: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: March 3rd

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

Tide Chat Summary: February 18th

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

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

Tide Chat Summary: February 4th

This post summarizes the 30-minute Tide status update and open floor discussion from February 4th 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

Announcements

Next meeting

The next meeting, a 2-hour active working session, will take place on February 18, 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

Tide Chat Summary: January 21st

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

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

Tide Chat Summary: January 7th

This post summarizes the 30-minute Tide status update and open floor discussion from January 7th 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 2-hour active working session, will take place on January 21, 2020 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: December 17th

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

Next meeting

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

This post summarizes the 30-minute Tide status update and open floor discussion from December 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

  • @derekherman been sidelined by work travel and holidays, will work to merge in various PRs (wptide#198, ) and deploy to GCP
  • Discussion continues on wptide#178 on whether its an update to the keys in the env file or if a code change is needed
  • Will reasses issues remaining in our next meeting after @derekherman merges existing PRs

Next meeting

The next meeting, a 2-hour active working session, will take place on December 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: 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