Review queue and theme maintenance tasks

We have gathered a list of tasks that the team needs to do regularly in order to maintain the review flow, besides reviewing themes.

If you feel “Oh yeah I can do that!” Please leave a comment, and we will include it in our spreadsheet and on the team members page.  If you are maybe interested, but you are not sure, you can ask team leads or moderators for more details.

  • Monitor report #22 to make sure no tickets are abandoned
    • Locating tickets that has had no replies within the last 7 days, and either close the ticket due to inactivity or return the ticket to the queue so that it can be picked up by a new reviewer.
    • Assigned to @rabmalin
  • Monitor report #16 to make sure no tickets were closed by mistake
    • Locate tickets that have been closed as not approved without cause, and return them to the queue.
    • Assigned to @kevinhaig
  • Monitor report #2 to answer general questions
  • Monitor the reports to make sure that authors only have one open ticket
    • Locating duplicate tickets, informing about the one theme policy and closing tickets as not approved.
    • Assigned to @bplv
  • Monitor report #24 to make sure no tickets were approved without a full review
    • Locate tickets that have been approved without a full review, and reopen them so that the reviewer can continue, or return it to the queue.
    • Assigned to @kevinhaig
  • Authors requesting new reviewers
    • Respond to authors who are requesting new reviewers, for example if the reviewer has not replied in 7 days.
    • Return the ticket to the queue.
    • Assigned to @bplv
  • Authors requesting tickets to be reopened
    • Respond to authors who are requesting their closed tickets to be reopened, for example if the theme was closed for less than five (required) issues.
    • Assigned to @imranaliweb
  • Reviewers requesting to be removed from tickets
    • Respond to reviewers who are no longer able to continue with the review.
    • Return the ticket to the queue.
  • Closing theme copies
    • Locating tickets where the theme is a copy of an existing theme, explaining to the author why, and closing the ticket as not approved.
    • Assigned to @imranaliweb
  • Closing and removing copies of commercial themes
    • Locating tickets where the theme is a copy of an existing commercial theme, explaining to the author why, and closing the ticket as not approved.
    • Notifying Otto42 so that the copy can be removed.
    • Assigned to @imranaliweb
  • Do follow-ups on live themes that does not follow requirements
    • Inform the author about requirements and request changes.
    • Inform the author of the possibility that their theme might be suspended.
  • Theme author transfer requests
    • Moderators who already have access to the back end can help with transfer requests. We are looking to assign  one or two “go to” people who authors can contact directly if they need theme transfers.
    • assigned to @djrmom

 

  • Weekly updates to https://make.wordpress.org/updates/
  • Bi weekly meeting agendas and meeting notes. Leading meetings
  • Monthly meeting agendas and meetings notes for MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team meetings

 

  • Monitor open Theme Review meta tickets
  • Revise documentation and requirements
  • Occasional posts to remind authors of upcoming major theme changes (coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. changes)

Every 6 months:

  • Theme reviewer badges
  • Promote theme mods / demote theme mods that has not reviewed in the last 6 months (access required)