|Projects||Summary||Related trac tickets or URLs||Maintainer(s)||To do||Completion time||Status|
|Readme.txt unification||A unified readme file across WordPress ecosystem is needed.|
One thing that could be implemented is the same readme on WordPress themes, as on WordPress plugins.
For this, a readme validator could be implemented (https://wordpress.org/plugins/developers/readme-validator/), and a number of things could possibly be made: a revamp of the themes pages on WordPress.org, theme sniffer validating readme etc.
Theme repository - add changelog listing tab
Feature Request: Readme.txt generated tabs on theme pages
Allow multiple screenshots
Theme Directory: Allow minimum WP and PHP version requirement
Support for theme changelogs
Show readme.txt from Themes
|* Come to an agreement about requiring the readme.txt to be valid before theme submission.|
* Communicate with theme authors on the importance of the unified readme files (making a blog post explaining why this is done and the benefits they'll have).
* Try to solve the meta tickets and talk to whoever is in charge (Otto) of making the changes to the themes page (design team would probably be needed for this part as well, as this impacts the wordpress.org site)
* Update the sample readme on the WPTRT repository and coordinate with #core-themes to have this unified readme in the twentynineteen theme
|Handbook update||With the recent release of the WPThemeReview coding standards, a handbook update should be in order.|
Current handbook has number of pages that are in the draft mode, some of the descriptions are out of date or not needed (some debugging tools).
It would be a good idea to align the handbook with the coding stanadards, in the same way WordPress Coding Standards are aligned with the core handbook.
Additionaly, we should align the standards categories with the handbook one, so that there is smaller chance of possible confusion when using automated checks on the theme.
|https://make.wordpress.org/themes/handbook/||* Make a blog post with a call to action for people to make a revision of the handbook.|
* See what items need to be added/removed.
* Come to an agreement of the general structure of the handbook (chapters, subchapters etc.).
* Add part about sniffer/phpcs checks and pasting the results in the trac ticket (how to): https://github.com/WPTRT/theme-sniffer/issues/58
|Theme unit test||Theme unit test data needs to be updated to include new editor (Gutenberg) support.||https://github.com/WPTRT/theme-unit-test||poena||* Add necessary checks, test the unit test by giving it to users so that they can report what needs to be added, or if anything is missing.|
* Clean the users from the import (?).
|Theme sniffer plugin||Theme sniffer plugin uses PHP_Codesniffer to sniff the theme using various WordPress related rulesets.|
Based on these sniffs, it will provide a report (per file) of possible issues.
This will help theme authors when creating a theme, and theme reviewers when reviewing a theme.
|https://github.com/WPTRT/theme-sniffer||dingo_d||* Fix the open PR https://github.com/WPTRT/theme-sniffer/pull/83|
* Modify the plugin structure
* Add integration tests
* Made updates to plugin with new features
|WPthemeReview||WordPress Themes for which a hosting application has been made for the theme to be hosted in the theme repository on wordpress.org have to comply with a set of requirements before such an application can be approved. Additionally, there are also recommendations for best practices for themes.|
This project attempts to automate the code analysis part of the Theme Review Process as much as possible using static code analysis.
PHP_CodeSniffer is the base tool upon which this project is build and is a PHP command-line tool.
This project is a work in progress and passing the checks is no guarantee that your theme will be approved.
|https://github.com/WPTRT/WPThemeReview||dingo_d||* Prepare for 0.2.0 release - sort the open issues and select which PRs to work on|
* Get more people to submit code examples - either theme authors or theme reviewers
|Trusted Authors program||The Trusted Authors Program is an attempt to streamline the review process for authors who are consistently able to show they can to produce high quality code and themes that are in line with the current guidelines.||https://make.wordpress.org/themes/2018/04/30/trusted-authors-program/|
|acosmin||* Re-evaluate the program to see if theme quality is reduced and if the program should continue|
* Make an entry in the handbook regarding rules and regulations of the trusted authors program
* Have an official list of trusted authors
* Work with design and core/meta team to create a trusted author badge