Jeffrey Paul 4:37 pm on January 27, 2021
Tags: ,   

Tide Chat Summary: January 26th

This post summarizes the Tide chat from January 26th (originally scheduled for January 19th) 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. http://php.net/manual/en/intro-whatis.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.

Node refactoring

  • @derekherman will move beta version of Node rewrite to https://github.com/wptide/ and make public
  • @derekherman will share link to related docs site that gets converted to HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. and deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. from markdown files in the repo, docs were completely rewritten to match Node version
  • wptide.org will stay in place until the updated Tide APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. output gets finalized
  • Node version will run in Staging until work is finalized, will then setup deploys to Production
  • @jeffpaul will look for folks to help test the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. Node version and be available to help pitch in on any remaining tasks to get Node version out of beta and functionally covering near term goals for Tide
  • NOTE from after the meeting:

I have moved the repository to the wptide organization and made it public. https://github.com/wptide/wptide.org This currently deploys develop to https://staging.wptide.org There are a few more things I was to sort out tomorrow and will give a full overview of where we are at. I’m heading off as it’s almost 2am. The API will most definitely change and if you are trying to test it just know it could be different in the next couple days.

Derek Herman in Slack

Next meeting

The next meeting, a 30-minute Tide status update and open floor discussion, will take place on February 2, 2021 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