Automation Meeting summary September 29, 2016

Items discussed

You can view the full meeting notes in the Slack archive. A Slack account is required.

@frankklein published a post on the background of the automation and why we have chosen ceratin tools.

All of the active contributors gave a quick update what they have been working on.

  • @grapplerulrich is working on coordinating contributions and looking to modularize the restricted function 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. 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..
  • @frankklein is working on underlying architecture/framework using phpDocumentor/Reflection library so that we can easily create sniffs to check the existence of files and functions as PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. is unable to do this. Codename `Theme_Analyser`
  • @kevinhaig has been working on automation every day since July. He has worked on `Abstract_ThemeSniff` and large number of other sniffs.
  • @jrf has been contributing upstream at WPCS and PHPCS to fix issues. She has also worked on utilities which should make the code for future sniffs easier.

We have set a few goals for the next meeting

  • Get a MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia for the `Theme_Analyser` so that others can review the code and start extending it.
  • Get the easy pull requests ready so that they can be merged.
  • Merge as many PR as possible.

The next meeting will be on the 13th October:

Channel: #themereview | Time: Thursday October 13th at 14:00 UTC 14:00 UTC