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 Agenda: July 16th

This is the agenda for the weekly Tide meeting on July 16, 2019 at 20:00 UTC:

  • 1.0.0
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #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 Agenda: July 9th

This is the agenda for the weekly Tide meeting on July 9, 2019 at 20:00 UTC:

  • 1.0.0
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #tide-chat

X-post: Updates to the WordPress User & Developer Survey

X-comment from +make.wordpress.org/updates: Comment on Updates to the WordPress User & Developer Survey

CANCELLED Tide Chat: July 2nd

This weeks Tide meeting originally scheduled on July 2, 2019 at 20:00 UTC has been CANCELED.

If you have anything to propose to add to next weeks agenda, please leave a comment below. See you then!

#agenda, #tide-chat

WordCamp EU Contributor Day!

WordCamp Europe 2019 Contributor Day was on June 20th. A very big thank you to all participants at the Tide table and the amazing cross team communication!

The day was originally going to be focused on-boarding new contributors to Tide, reviewing the backlog for issues, and submitting pull requests. As well, I had planned to meet with the Hosting team after lunch and connect with the Meta team to discuss how we can start consuming data from the Tide API.

The actual event went something a bit different…

As usual the WiFi network was overtaxed and getting people setup with Tide was a bit of an arduous task. Unfortunately, we were not able to get anyone setup with a local working version of Tide.

Instead effort was put into fixing issues that could be done without installing the Tide requirements and building the Docker images. For example, the documentation and API results. There were a couple pull requests created by @ottok as a first time contributor, which deserves a big thank you!

@grapplerulrich and I also began focusing on installing the wordpress.org meta environment to trying and create a patch that would consume the Tide API and display those results. Again the WiFi played a hand in slowing down that effort. The biggest win though was all the cross team communications.

Luckily we were able to get the right person at the table, thank you @dd32! Dion updated the meta environment so the Tide PHP Compatibility results for plugins are now being stored with the post meta. We are officially using the Tide API and it feels good!

What does that mean though? We are not yet consuming data for themes, we are in the exploratory phase where we test that the sync is working correctly. Once we are satisfied that the connection is stable we will add data from themes. Then we can explore the logic and UI needed to expose that data to everyone and respect the authors supplied value.

We are much closer now to using the TIDE API to automate static analysis on plugins and themes. It’s a small piece of code but a huge win for the project. There was also discussion of ways to use Tide in a broader sense and we are now looking towards the future. This is especially important for automating review team activities and for helping WordPress adopt PHP 7+ — it’s exciting to say the least.

On Saturday I also had the pleasure of meeting with several folks to discuss the requirements for the Plugin & Theme Review teams plus what actions need to be taken to move the coding standards into a good place for our community. There is a recap of that conversation here.

The biggest takeaway of the event is that Tide is now being used. However, we have a lot of data to analyze currently in our API, which could be used to solve whether or not WordPress is ready to adopt a more modern codebase. I have a few more meetings to attend and ideas to formulate on the future of Tide, so look for those updates in the coming weeks.

For now let’s all just celebrate this win!

CANCELLED Tide Chat: June 25th

This week’s Tide meeting on June 25, 2019 at 20:00 UTC has been cancelled due to folks traveling back from WCEU.

If you have anything to propose to add to next week’s agenda or specific items related to the above, please leave a comment below. Thanks!

#agenda, #tide-chat

Tide profile badges

If you are a maintainer or contributor to Tide, then you may have noticed that Tide Team or Tide Contributor badges have been added to your WordPress.org profile pages (example here). In short, maintainers receive the Team badge while contributors receive the Contributor badge.

The Team badge uses the Tide dashicon with a light blue background and the Contributor badge uses the Tide dashicon with a plain white background:

Tide Team

The Tide Team badge will be manually assigned to all active Tide maintainers – i.e those who are listed as “Maintainers” on this page (also here).

Tide Contributor

The Tide Contributor badge will be manually assigned to those who provide valuable contributions to Tide — i.e. those who are listed as “Contributors” on this page (also here, here, and here).


The easiest way to have the Tide Team or Tide Contributor badges assigned to you is for you to request them (the system doesn’t allow us to add the badge to your profile until you submit a request). To make this request please go the Tide Team or Tide Contributor pages and request membership for the group.


To find out more about how to get involved, please check out the Tide Contributing Guide.

We hope that with these new badges, we will be able to recognize all of the work that so many people do to grow the Tide project all around the world!

#badges, #profiles

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