Automation Meeting October 27

In the last meeting on October 14 not everyone was able to attend who are contributing. Here are the belated meeting notes from the last meeting.

  • There was an issue 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. that was causing the travis tests to fail when we used PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. master branch, This has been fixed and we have merged the latest into the TRT/WPCS develop branch. All travis tests should be passing again.
  • I have made progress with the pull request to modularise the restricted functions upstream in WPCS. Hopefully it will get merged till the next meeting in two weeks.
  • I have started rebasing Kevin’s pull requests and making updates to the inline docs and making changes from the code reviews.
  • We had a few questions but no major discussions.

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 27th October 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.