Update queue process

In the attempt to work out what steps we need implemented and what we need to build. Here are the steps we are looking at for the updated queue. This is the process a theme will go through when updated. Note: this is a work in progress and some things need to be talked about.

1. A theme is updated in the normal way.
2. The theme check 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 runs over the theme.
3. If theme check passes, the theme goes live.
4. If theme check fails, the theme doesn’t progress until it’s passed.
5. If the theme goes live, no tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket is made (or is.. see questions).
6. We need a queue of recently updated tickets – note this may need tickets or something to indicate this. This queue is only for people if want to check updates.
7. A button is on all themes in directory. This button is ‘report this theme’.

Report theme process
1. The report button is clicked.
2. If logged in the reporter is logged and also a ticket made and put in reported queue.
3. The theme review team monitor this queue as a priority. Once a ticket appears there someone takes it and does a full review.


  • Should we make tickets but not count them as open?
  • Do we need tickets to have a trac of what has happened to the theme?
  • Do we have to log the reporter of the report theme button? It could act as a good citizen effect and make people think before clicking.
  • Should we add a step to the button to get the reason reporting?