Tide Chat Summary: December 5th

This post summarizes the Tide chat meeting from December 5th 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 (Slack archive).

Discussion highlights

Tide priorities

  • Priority is working to integrate 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/
  • Success is defined as seeing 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 and error/warnings on WordPress.org pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme pages
  • Will need to work through UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. of what’s best to display on WordPress.org (@joshuawold @maximsiebert working through options)
  • We need to figure out exactly where the Audit Server & 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. is going to live and whether we’re moving to GCP (not an easy lift) from AWS or if this will be hosted on the .ORG servers (@chanthaboune @barry to provide input)
  • Next step is to define actions to integrate Tide into WordPress.org, who owns each action, and a timeline for each action
  • Once Tide has been integrated into WordPress.org we’ll reassess community input and move on to what’s next most impactful for the community
  • If you have ideas, please comment on this post and we’ll collect them for prioritization post-integration

Tide documentation

  • The following items need to be assembled to start working as a community:
    • Correct wptide.org redirects to correctly go to make.wordpress.org/tide (aka “make/tide”)
    • Open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. Tide repo
    • Open source Tide documentation + architecture diagram (dependent on integration with wp.org details, @joshuawold to clean up diagram of current ecosystem)
    • Create Tide handbook pages (e.g., code/issues/release planning lives on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, deadlines aren’t arbitrary, background on the creation of Tide, you can use phpcbf to fix the easy stuff)

Tide contributions

  • Will need to figure out how best to support community contributions, dependent on final infrastructure
  • One way of contributing indirectly would be to get involved with the various projects/standards used to generate audit results: PHPCS, WPCS, PHPCompatibility, Theme Review team standards

General announcements

  • Where can I see results like I saw at the Tide booth at WCUS?
    • While there is not an immediate timeline, that will happen as soon as we can finish the integration into WordPress.org.

Next week’s meeting

The next meeting will take place on Tuesday, December 12, 22: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