All plugins submitted to the ClassicPress Plugin Directory will be reviewed by the Plugin Review Team. The basic process used for reviews is outlined below:
- Verify that plugin name and its purpose are acceptable.
- Verify the presence of a GitHub release link, and download the release zip.
- Make sure the readme file does not contain spam, bad links or other unacceptable content and check for the required plugin headers.
- Run plugin through CPCS to check for major issues. Tabbing, indenting, naming conventions, code formatting and other minor issues will be ignored.
- Run plugin through pluginvulnerabilities.com to check for potential issues.
- Check plugin for Plugin Directory Guidelines violations.
- If issues are found, email developer from [email protected].
- If no issues are found, approve plugin and email a confirmation to developer. Also invite developer to create a release post in the Plugins Forum.
- Once approved the plugin has to be mirrored in the repository here. This is solely used as a backup and development resource.
- Each time ClassicPress releases a major version, an email is sent to the developers, two weeks ahead of the release, reminding them to test their plugin against the new ClassicPress version. Not taking action may result in delisting of the plugin.
The review process will be quicker and smoother if you are familiar with the Plugin Directory Requirements in addition to the Plugin Directory Guidelines.
Escalation
If you are not satisfied with the review process, you can escalate it by sending an email to [email protected]. Include a detailed explanation for the escalation.
Avoidance of conflict of interest
A plugin reviewer may not review a plugin he/she has direct involvement in. However, reviewing the plugin is allowed if reviewer previously gave support to the developer via the official ClassicPress support channels.