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

Tide Chat Summary: March 12th

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

  • There are currently 8 open issues in wptide and 1 in docs for 1.0.0. @valendesigns is working through some of these, but looking for others available to assist on PRs.
  • A couple good-first-issues related to the documentation on wptide.org for those looking to explore a little on Tide.
  • @cathibosco1 to help with a favicon for wptide.org (see wptide#176)
  • @valendesigns to open issues from recent testing, generally around caching issues

Tide Dashicon

  • Discussion on core#41074 in devchat last week, a pento-shaped person will look into reviewing/committing the patch to add the Dashicons that have been ready since the 4.9 release cycle (including the Tide Dashicon).

Next meeting

The next meeting will take place on March 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: March 5th

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

  • Beta2 deployed to GCP on February 28th, updated docs are now live on https://wptide.org
  • More descriptive and accurate docs thanks to @kkoppenhaver and others from WCUS 2018
  • Looking for feedback on the updated wptide.org and related docs
  • @valendesigns fixed some bugs and updated coding standards and PHPCS, everything milestoned as 1.0.0 still seems relevant
  • RC pending, so please call out anything you think NEEDS to land in 1.0.0

Tide Dashicon

  • Trac#41074 discussed in Design meeting on Monday, being added to Core devchat this week
  • Assumption is that the patch is ready to land in 5.2, but just want to confirm that nothing else significant is needed
  • Special thanks to @CathiBosco1 for helping push on this

General announcements

Next meeting

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

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

  • Continued search for folks to help with documentation and testing, please reach out if you’re available.
  • Also continued search for folks with Go and/or Google Cloud Platform experience to help finish off items for Tide 1.0.0, please reach out if you’re available.
  • No additional issues/PRs noted for inclusion in 1.0.0-beta2, so working through the existing set of issues/PRs is the current plan
  • @valendesigns working on the docs PRs, got the pkg PR tests fixed, working to get beta2 out in near future

Tide Dashicon

  • Working to find someone to help land a patch on #41074 now that trunk is open for the 5.2 release cycle in core
  • Long-running project to convert Dashicons to SVG not likely to wrap soon, so @jeffpaul to continue looking to get Dashicons update merged at beginning of WP 5.2 release cycle

General announcements

  • @williampatton looking into Tide’s application to the Theme Review process (see Slack thread for more info)
  • hoping to hear more as that testing proceeds and what enhancements from Tide might better support the needs of the Theme Review Team

Next meeting

The next meeting will take place on February 26, 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: February 12th

This post summarizes the Tide chat meeting from February 12th 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-beta2 + documentation

  • Continued search for folks to help with documentation and testing, please reach out if you’re available.
  • Also continued search for folks with Go and/or Google Cloud Platform experience to help finish off items for Tide 1.0.0, please reach out if you’re available.
  • Discussion on current docs process and site, will investigate Gutenberg handbook documentation process to see if it would apply well for Tide
  • Looking for simple/easy way to push docs up to a site like wptide.org from a GitHub repo

Tide Dashicon

  • @cathibosco1: Marketing team let us know that Community-team handles the stickers and pins for WordCamps, sent request to #community-team channel to get Tide icon added to the collection
  • Long-running project to convert Dashicons to SVG not likely to wrap soon, so @jeffpaul to continue looking to get Dashicons update merged at beginning of WP 5.2 release cycle

Theme Review Team

  • @joyously joined the chat to follow discussion from #themereview meeting on possibly leveraging Tide with the Theme Sniffer
  • Tide could utilize TRT ruleset and audit the existing themes and then all new submissions/updates, could also integrate other theme-specific rulesets as desired
  • Existing themes could be audited in a couple of hours, but work would be needed to support the new ruleset and specific integration with TRT tools and processes
  • Will investigate this further after .ORG integration of PHP Compat data

Next meeting

The next meeting will take place on February 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: February 5th

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

  • @valendesigns reviewing wptide#173 and docs#19 to merge into 1.0.0-beta2
  • Otherwise looking to complete work on the failed tests in pkg before cutting the 1.0.0-beta2 release
  • If you have PRs you’re working on, let us know so we can try and get them into 1.0.0-beta2

Tide Dashicon

General announcements

  • We continue to search for folks with Go and/or Google Cloud Platform experience to help finish off items for Tide 1.0.0, so please reach out if you’re available… thanks!

Next meeting

The next meeting will take place on February 12, 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: January 22nd

This post summarizes the Tide chat meeting from January 22nd in the #tide Slack channel (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.

Tide Dashicon

General announcements

  • For those with availability and interest, please review and provide feedback to the Our Strengths and Challenges post on Make/Updates
  • We continue to search for folks with Golang and/or Google Cloud Platform experience to help finish off items for Tide 1.0.0, so please reach out if you’re available… thanks!
  • Note that @jeffpaul will be out-of-the-office and unable to run Tidechat on January 29, 2019 so we’ll take a one week break on Tidechat and come back to meet in February.

Next meeting

The next meeting will take place on February 5, 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: January 15th

This post summarizes the Tide chat meeting from January 15th in the #tide Slack channel (\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-beta2 timing

  • Proposal to merge wptide-PR#173 and docs-PR#19, then tag 1.0.0-beta2 with any other updates ready to land
  • Next step will be ensuring docs on wptide.org are accurate and there’s a straightforward way to manage them (ideally via a GitHub repo or /docs/ folder)
  • Docs need to be stable (see above) and the pkg-PR#17 needs tests fixed before 1.0.0-beta2 can be released

General announcements

  • Note that WPCS 2.0.0 was released this week
  • @cathibosco1 making progress on getting Tide dashicon available for use on Make/Tide and other marketing efforts

Next meeting

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