WordPress.org

Theme Review Team

Welcome to the Theme Review team.

We are a group of volunteers who review and approve themes submitted to be included in the official WordPress Theme directory.

The Theme Review team maintains the official Theme Review Requirements, the Theme Unit Test Data, and the Theme Check Plugin.

We also engage and educate the WordPress Theme community regarding best practices for themes.

Interested in joining the Theme Reviewers team?

Great! The team is open to anyone who wants to help out, and the process is simple. To find out more just visit the Join The Team page.

Want to know more? There is a more information in the Theme Review Team’s Handbook and the Review itself.

Once you get a theme to review, you will also get a mentor to help you on the road to becoming a theme reviewer.

Weekly meetings

We use Slack for real-time communication. As contributors live all over the world, there are discussions happening at all hours of the day.

We have a project meeting every Tuesday at 18:00 UTC in the #themereview channel on Slack.

There is also a second meeting temporarily on Thursday at 18:00 UTC in #themereview

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Tammie 6:23 pm on June 30, 2015 Permalink |  

    Theme review team weekly meeting notes

    The logs are here:
    https://wordpress.slack.com/archives/themereview/p1435687161000567

    Points from meeting:

    • Creating Useful tools page and linking in handbook. Will add all tools there. Please let us know your tools for theme review. This includes theme checkers, plugins for reviewing.

    We had a short meeting. There are no plans for a meeting on Thursday so see you all for the roadmap meeting on next Tuesday.

     
  • Tammie 10:04 am on June 30, 2015 Permalink |  

    This week’s meeting agenda

    We have a meeting at 18:00 UTC today in #themereview. Lets talk about tools. We have a few things around to make reviews and reviewing easier. There are a starting to be some new projects also. Lets have a few topics:

    • Does anyone have an idea for a tool they need support with?
    • How can we help those with tools?
    • What tools are going on? Can we collate a list somewhere in resources? We don’t want to recommend yet. It’s worth noting that getting a tool to be officially supported (none beyond the theme check and doing_it_wrong_theme is) and on Github repo is another step and requires design, ux, code review and decisions. However, should we link from handbook as useful links?

    If you have anything else you’d like discussed please raise it here.

     
  • Tammie 7:18 pm on June 23, 2015 Permalink |  

    Theme review team weekly meeting notes

    The logs are here:
    https://wordpress.slack.com/archives/themereview/p1435082246001621

    Points from meeting:

    1. Directory survey: https://make.wordpress.org/themes/2015/06/22/survey-results-directory/

    • We should reconsider our keywords in our roadmap. Can we automate them? Can we have people able to update them?
    • We need to do a survey just on tags.
    • We began talking about how we should improve the admin interface for those with themes on org. The UI needs to be more friendly. How can they manage their entire theme?

    Actionables: @greenshady to think about tags and with me come up with survey suggestion. @grapplerulrich: to get an easy cull list of tags. Add to roadmap: tag survey, redoing tags, theme admin on org.

    2. Review survey: https://make.wordpress.org/themes/2015/06/22/survey-results-review/

    • Documentation is an issue. Could this be a language issue?
    • We talked about setting expectations for review time. This could be added to the uploader intro we are going to think about adding licenses to.
    • Would partial reviews be a solution, or do they cause more issues and create a bad experience?
    • Auto approving updates can speed up queues.
    • More we automate the better our queues.

    Actionables: @grappleulrich is moving the button to help with abandoned. v2 of the workflow will be put as make.blog post before our planning meeting on July 7th.

    3. Using WordPress.org themes survey: https://make.wordpress.org/themes/2015/06/22/survey-results-using-themes-from-wordpress-org/

    • We should consider in our roadmap the preview.
    • @otto42 is working on the preview and we should support what he is doing. This will bring the customizer to the front end securely. The user can then change things.
     
  • Ulrich 12:02 pm on June 23, 2015 Permalink |  

    Reducing the number of tickets that need to be reassigned 

    Previously I wrote about the new report that was created to track tickets that needed to be reassigned. Through this method we have successfully reassigned a large number of tickets. This tracking does not solve the root problem of the many tickets that need to be reassigned. A number of ticket have had no activity from the reviewer after they have been assigned. This leads me to believe that some people click on the review button in the sidebar by mistake as it is on every page.

    We previously discussed to create a page where we would place the button. I have now created this page. I have added some content. The next step would be to remove the button from the sidebar and replace with a link to the “Request a theme to review” page.

    Discussion points are:

    • Should we make the change? Can the text be improved on the “Request a theme to review” page?
    • What other things can we do to prevent tickets needing to be reassigned?
    • What can we do to get the tickets reassigned quicker?

    One idea to get tickets reassigned quicker is to include the tickets in “Report 30” to be assigned when a reviewer with more than 5 completed reviews clicks on the button.

     
    • Omaar Osmaan 2:55 pm on June 23, 2015 Permalink | Log in to Reply

      +1 for the change. Currently “Clicking this button will assign you a theme. Do not click it if you are not a reviewer or if you do not want a theme assigned to you. ” is a misleading description, many people wont read the message and click the button just to see what happens- and many will click the button ’cause you’re saying not to- a lot of people react opposite in such case- :)

      Suggested flow is way better. I would suggest to remove the mentioned message entirely from the sidebar, just keep the title and button (or only the button) and linked it to the “request a theme to review” page.

      The text on the “Request a theme to review” looks good, but I would suggest to place the button on that page below the warning message. That will defuse more people who aren’t actually interested to do the job, from clicking on that button.

      • Ulrich 5:50 pm on June 23, 2015 Permalink | Log in to Reply

        So a better warning would be
        “Only click the button if you want to review a theme”

        Suggested flow is way better. I would suggest to remove the mentioned message entirely from the sidebar, just keep the title and button (or only the button) and linked it to the “request a theme to review” page.

        That is the idea sorry if it did not come across like that.

    • Tammie 4:20 pm on June 23, 2015 Permalink | Log in to Reply

      I agree having a page is good. But, we should link from the sidebar – we have to think of ease of use for new reviewers. Linking to the page that is not directly to download. We also should look into adding the queue to the list of themes people get auto assigned.

      • Ulrich 5:53 pm on June 23, 2015 Permalink | Log in to Reply

        But, we should link from the sidebar – we have to think of ease of use for new reviewers.

        The idea is to add a link in the sidebar to the page. I think we are saying the samething.

        We also should look into adding the queue to the list of themes people get auto assigned.

        Which queue did you mean? The update queue?

    • niknetniko 1:07 am on June 28, 2015 Permalink | Log in to Reply

      Well, since I can’t find a better place to say it, I am one of those people who accidentally clicked it, and now I’ve got a ticket assigned to me. Is there a way to un-assign?

      • Ulrich 7:23 am on June 28, 2015 Permalink | Log in to Reply

        @niknetniko – I must ask how did you accidentally click on the button now that we have moved the assign button to a separate page with a big warning? The reason I ask is that we are trying to prevent people from accidentally clicking on the button.

        I have added the theme to a list to be reassigned.

        • niknetniko 10:56 am on June 28, 2015 Permalink | Log in to Reply

          @Ulrich Thanks! I was reading this page (https://make.wordpress.org/themes/handbook/review/recommended/) in the handbook, and the first thing in the sidebar is a big button ‘Request a theme to review’. I was going for the navigation above, but my touchpad failed me and clicked the button instead, and then I had a theme assigned to me.

          • Ulrich 4:34 pm on June 28, 2015 Permalink | Log in to Reply

            @niknetniko – Thank you for reporting this. We wanted to change to the button with a link to a page with a button and I missed the one on the handbook page.

            It may take a few weeks till the ticket is reassigned. If you find time during this time to a theme review I would be happy to help you along the process. If not then it will be reassigned in a few weeks.

            Please could you mention in the ticket that you click on the button by mistake so that the theme authors knows what is happening. Thanks.

            • niknetniko 4:44 pm on June 28, 2015 Permalink

              @Ulrich I’ll do that. I’ll also see if I have the time, I will have an in-depth look at the handbook, and if possible I’ll review the theme. It depends on how much time I can find, really.

    • Nilambar Sharma 5:20 am on June 29, 2015 Permalink | Log in to Reply

      May be we could check last commented date by `Owner` to find out whether ticket is actively reviewed. If it is more than 7 days then we can move it to Report 30. It is great idea to assign Report 30 ticket if requester is Reviewer. If requester is Trainee reviewer then assign ticket from Report 2.

      • Ulrich 8:41 am on June 29, 2015 Permalink | Log in to Reply

        One of the challenges that we face is that there is no way of knowing when a ticket was last modified by an reviewer. My problem with the doing something after 7 days is that sometimes the reviewer may have a special agreement with the theme author to wait longer.

        I would love to stop tickets needing to be reassigned. I will be trying to track how many tickets get assigned via the button over the next week or so. https://themes.trac.wordpress.org/report/29

        We can’t look from yesterday as WCEU hat their contributor day.

  • Tammie 7:34 pm on June 22, 2015 Permalink |  

    This weeks meeting agenda.

    We’ve got a meeting on Tuesday at 18:00 UTC in #themereview.

    Lets have an open floor to discuss the survey results.
    https://make.wordpress.org/themes/2015/06/22/survey-results-using-themes-from-wordpress-org/
    https://make.wordpress.org/themes/2015/06/22/survey-results-directory/
    https://make.wordpress.org/themes/2015/06/22/survey-results-review/

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel