Tide Chat Summary: May 15th
This post summarizes the Tide chat meeting from May 15th in the #tide SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel (agenda, Slack archive).
Reminder that the current Tide focus is integrating PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. Compatibility data from Tide into WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. Once PHP Compatibility is integrated into WordPress.org, we’ll assess the next focus to provide the biggest impact to the community.
Roadmap wishlist
- Currently collecting ideas, will asses feasibility, and share roadmap as its ready
- Discussion on things PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. is unable to check for that would benefit the #ThemeReview Team (@grapplerulrich, @joyously, @valendesigns):
- if you are a child or parent theme
- If a theme has a specific tag in the `style.css` if a certain `add_theme_support()` is defined in the `functions.php`
- A specific example would be the `custom-headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.` tag with `add_theme_support( ‘custom-header’ );`
- The problem is that PHPCS only checks things per file and can’t remember what it has already checked for.
- things that coordinate between files
- It would require checking for `add_theme_support` and building an array then verifying that it’s tagged in the header.
- Benefit is that it would help verify that a theme is actually adding the support for a feature if it using the tag or that if a theme has the feature then it should be tagged correctly so to make it better to search for.
- Additional details are listed in WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016. issue#578 under Rules which would need another solution
- We would have to add a new server with a new audit type and wouldn’t be in the phpcs payload
- If you have roadmap wishlist ideas, then please leave them as a comment on this post, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @jeffpaul directly, comment in the #tide channel, or add your input as an issue in the `tide-issues` repo and we’ll capture them as we work towards publishing a potential roadmap for Tide
GCP migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.
- We are currently switching to the Google SDKs and then will test everything on GCP. There will be a new repo coming very soon.
- We will be looking for help testing very soon to setup the new repo, but the goal is to keep the option to use AWS or GCP and, if we can, a local-only option
- Google Storage and S3 are easy to replace locally. However, SQS is not as easy to replace locally and we’re planning to use Firestore on GCP so two very different solutions that when trying to create a local queue is a bit more work and may not be ready by next week.
- The migration to GCP and rebuild of the server in Go will ideally be ready for WCEU
Next meeting
The next meeting will take place on May 22, 2018 at 21:00 UTC / May 22, 2018 at 21: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.