Automation Meeting November 10

The last meeting was on October 27, we discussed the following items.

  • A number of sniffssniff A module for PHP Code Sniffer that analyzes code for a specific problem. Multiple stiffs are combined to create a PHPCS standard. The term is named because it detects code smells, similar to how a dog would "sniff" out food. were merged in: Check that the <title> tag is not used, that favicons are not used, add a warning if people are using include, restrict a list of 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 territory functions and add escaping and sanitization warnings, disallow the use of the backtick operator (shell commands).
  • I have made further progress with the pull request to modularise the restricted functions upstream in WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook.. There was a travis test issue which has been fixed in the mean time.
  • @jrf has been helping reviewing the open pull requests to get the ready to be merged and getting utility functions merged upstream so that it will make live easier for us.
  • @miyauchi has started to develop A WP-CLI theme test system. This should allow theme developers to have a way to test their theme automatically with something like travis. https://github.com/miya0001/wp-cli-scaffold-theme-tests
  • @frankklein has the scaffolding to parse the theme, and run some checks, and print a report. The big item he is working on now if modifying the parser logic to focus on the functions used inside custom functions and methods. He is using the same code as the one that creates the data on https://developer.wordpress.org/reference/

Channel: #themereview | Time: Thursday at 14:00 UTC 14:00 UTC

The goal of the bi-weekly meeting is keep other informed on the progress of the project and discuss any issues.

The agenda for the 10th November will be

  • Short update from the contributors what they have worked on.
  • Define goals for the next meeting.
  • Discuss any open issues and/or pull requests that need attention.

Pinging @poena, @frankklein, @pross, @jrf, @shinichin, @miyauchi

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

The next meeting is on Thursday, November 10.