Tide Chat Summary: June 11th

This post summarizes the Tide chat meeting from June 11th 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 open in the milestone
  • 3 issues pinned to Issues page that are great opportunities for new contributors:
    • wptide#178: an update to the API client; @kkoppenhaver may be able to pitch in on this one
    • wptide#100: review and update on our Windows local install instructions; @fahimmurshed still planning to pitch in on this one
    • wptide#170: helping to finish up docs on how we handle Tide Team and Contributor badges

General announcements

Next meeting

The next meeting will take place on June 18, 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: June 4th

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

  • Still continues to have 8 open issues in the milestone with also two good first issue items in there for folks who are new to Tide and looking to contribute
  • For Windows users, we’d love some help on wptide#100
  • For those comfortable with API work, we’d love some help on wptide#178
  • Some other non-1.0.0 issues related to the docs site that are also helpful for new contributors to help with
  • In general, going through the local setup instructions and calling out any discrepancies or issues you run into is also massively helpful. This ensures that others have as good an on-boarding experience as possible with Tide.
  • @fahimmurshed reviewing Windows local setup instructions, will follow up with any issues/updates

General announcements

  • Sharing a callout from @chanthaboune on the Team Lead Interest Post over on the Make/Updates blog; if you’re interested in learning more about team leadership, then please give that a read

Next meeting

The next meeting will take place on June 11, 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: May 28th

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

  • Same as last week with 8 items remaining in the milestone
  • @valendesigns deployed changes to App Engine last week, also pushed the new Docker images and redeployed the Kubernetes cluster for the PHPCS Server that’s now using WPCS 2.1.1 for new plugins/themes
  • Some items in the docs repo that aren’t targeted for the 1.0.0 release, but are otherwise helpful things to tackle
  • some good first issues for new contributors as well

General announcements

Next meeting

The next meeting will take place on June 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: May 21st

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

  • Down to 8 items open in the milestone
  • Two good first issue items for folks looking to get into contributing to Tide (wptide#100 & wptide#178); we would welcome a PR for either of those!
  • @valendesigns was able to fix the build for wp-tide-api that was failing
  • Initial deploy to App Engine included all the theme changes but another deploy is needed to include the updated images for all the servers, which includes WPCS 2.1.1 support for PHPCS
  • @valendesigns also tried to upgrade to WP 5.2 in the API image but had to rollback locally otherwise most of the tests fail for wp-tide-api plugin
  • Appears to be a bug that is caused by a change on the .ORG side where it seems the download URL for specific versions of themes/plugins no longer works. If we’re not able to track down how to get access to the archives, then we will need to add SVN support to the PHPCS server to checkout the correct version of the code.
  • Right now it appears that only the most recent version of a plugin/theme is available to download.
  • So if someone from the Plugin or Meta team is around that knows how to access the plugin/theme archives that would be awesome!

Next meeting

The next meeting will take place on May 28, 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: May 14th

This post summarizes the Tide chat meeting from May 14th 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-rc

  • 9 open issues still remain in the 1.0.0 milestone
  • A couple good first issue ones in there for those interested and able to help out, would love to see PRs for them (wptide#100 & wptide#178)!

General announcements

  • @valendesigns spoke with WCEU organizers and he’ll be running the Tide table at Contributor Day; please call out if you’ll be there and plan to assist or stop by
  • In order to update the docs on wptide.org, it requires a manual deploy to App Engine with a Make command; @jeffpaul to work through some backlogged issues/PRs in the docs repo

Next meeting

The next meeting will take place on May 21, 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: May 7th

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

  • 9 issues still remain in the milestone
  • Two good first issue in that list in case folks want to contribute in this release: wptide#100 and wptide#178
  • We continue to look for folks in the community who are interested and available to contribute to these 9 issues in the 1.0.0 milestone, please reach out if that’s you!

General announcements

Next meeting

The next meeting will take place on May 14, 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: April 23rd

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

  • Work continues on getting Tide ready for .ORG integration of PHP Compat data
  • 9 issues in the milestone
  • @valendesigns had less time lately than desired, will work on review and merging as time allows
  • Biggest remaining issue is caching

General announcements

  • If you’re headed to WCEU and plan to be at Contributor Day, please let @valendesigns know if you’d be able to help at the Tide table

Next meeting

The next meeting will take place on April 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.

#summary, #tide-chat

Tide Chat Summary: April 9th

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

  • Currently 9 open issues in the milestone
  • If you have a Windows machine, help would be appreciated on wptide#100, testing the local setup flow to see what’s different in Windows and helping capture updates for the docs there
  • @valendesigns aiming to review PRs this week
  • Closing wptide#152 in favor of MetaTrac#4309, will handle updates in Meta Trac as the visual HOW the Tide data gets displayed on .ORG is generally outside our control (though something we generally would like to have input on)

General announcements

  • For issues outside the 1.0.0 milestone, wptide#178 and wp-tide-api#22 would be valuable areas for contribution
  • Same for wptide#165 and how it could possibly be added as a separate plugin alongside Tide’s core services

Next meeting

The next meeting will take place on April 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.

#summary, #tide-chat

Tide Chat Summary: April 2nd

This post summarizes the Tide chat meeting from April 2nd 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-rc

  • @valendesigns continues to work through issues/PRs in the milestone, though we continue to look for any help from others as well
  • Some new issues and PRs in the docs repo, thanks to those helping review and assist there!

Tide Dashicon

General announcements

  • @jeffpaul added GitHub alerts for the various Tide repos to the Slack channel
  • Alerts for comments were included, but that quickly got too chatty so they were removed

Next meeting

The next meeting will take place on April 9, 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: March 19th

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

  • Currently showing 9 open issues in wptide and 1 open issue in docs for 1.0.0
  • So far @valendesigns is singularly working through PRs, so any additional assistance would be warmly welcomed!

Tide Dashicon

  • Update since Tidechat: core#41074 was committed today and the Tide Dashicon as well as other icons added since 4.8 are now available in the 5.2-beta release
  • And update to the developer.wordpress.org page template is needed to have the newly committed Dashicons appear

General announcements

  • @jeffpaul is offline next week, so we will skip next week’s Tidechat and resume on Tuesday, April 2nd

Next meeting

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