Team meeting: queues

Note: These are all in note form from the team meetings that took place over 2 days after the WordPress summit. When words like everyone and we are used, they are done for the group that was there. This was a cross section of the people who review and work on this project.

This meeting’s objective was to discuss the queues.

Should we remove numbering?
Child themes are different case.
We need a better workflow.
Maybe looking at the way core tag first patch is good.
GPL compatible tag? Maybe this works better with lack of resources.
Maybe low hanging tasks like checking GPL and screenshots are a good entry point for reviewers. We joked about having a GPL police force.
It’s not clear anyone can comment on any ticket.
Time it takes to review a theme is a problem. Process is too long.
Why does a review take so long?
Theme reviews take time:

  • code review
  • frameworks
  • time that it takes to review is elastic

Should we be reaching out and educating about better themes.
Who are we when we contact people?


  • Outreach program can also be used to stop the code coming in the first place.
  • We should be spreading the word about theme review process. Locally and making sure that the word gets out.