Meeting notes for 2017 September 26

Meeting [ link ]. A Slack account is needed to view the archives.

Items discussed:

  • New team leads.
    • @rabmalin and @thinkupthemes have been chosen by current leads to be the next team leads.
    • Current team leads will be stepping down sometime in October. Exact date to be confirmed.
    • Plan is for the new leads to remain in place for 6 months. Future succession plans will be decided in future.
  • Core ticket #37661-core. Potential removal of featured section and changes to tags.
    • Plans to improve customizer experience to allow users to install themes from the directory directly from within the customizer.
    • Core have proposed removing themes featured section in the admin area of the users website.
    • Possibility that this will in time lead to the removal of the featured themes section on wordpress.org also.
  • Content creation. (Can themes have content creation if the content is saved).
    • Proposal for an approach which allows for content to be retained by users following a theme switch was presented. This relates to content that would otherwise usually be created via a companion theme specific plugin.
    • The content would be available to the user, presented in the post content of a page following theme switch, allowing the user to easily continue to use the content in future.
    • No changes have been made to the content creation guidelines following the outcome of the discussion.
  • Progress update on adding Theme Sniffer to theme upload page.
    • Next steps are to update the Theme Sniffer to the latest version of PHPCS which is 3.0.1 and PHPCs 0.13.0.
    • New version of Theme Sniffer plugin planned for release once all existing Pull Requests and Issues have been addressed.
    • Outstanding issues can be found here: https://github.com/WPTRT/WordPress-Coding-Standards/issues

 

 

#themereview

Agenda for 2017 September 26

The Theme Review Team holds a fortnightly meeting and we encourage all members to attend.

Channel: #themereview | Time: Tuesday, September 26, 2017 at 17:00 UTC 17:00 UTC

The following will be discussed during the meeting:

  • New team leads.
  • Core ticket #37661-core. Potential removal of featured section and changes to tags.
  • Content creation. (Can themes have content creation if the content is saved).
  • Progress update on adding Theme Sniffer to theme upload page.
  • Applying Theme Sniffer to existing available themes.

The meetings typically last 30 minutes, however may last up to 60 minutes. If time permits, additional topics may be discussed.

If you would like to discuss additional topics to those mentioned above, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

#37661-core

Open floor notes for September 12, 2017

A Slack account is needed to view the archives.

  • Child theme names [link]
  • Global admin notices [link]
  • Display author email addresses [link]
  • How-to review page draft [link]

September/October meeting times

Tuesday, 5th of September – No meeting

Thursday, 7th of September – “How to do a review” document meeting (formerly requirements rewrite)
Channel: #themereview | Time: 2017-09-7 17:00 UTC 17:00 UTC.

Tuesday, 12th of September – Open floor meeting
You can suggest topics by posting a comment. Let us know if you want to lead this meeting.
Channel: #themereview | Time: 2017-09-12 17:00 UTC 17:00 UTC.

Tuesday, 19th of September – No meeting

Tuesday 26th of September – Team meeting.
This meeting will be lead by @thinkupthemes.  Agenda will be posted at a later date. You can suggest topics by posting a comment.
Channel: #themereview | Time: 2017-09-26 17:00 UTC 17:00 UTC.

Tuesday, 3rd of October – No meeting

Tuesday, 10th of October – Open floor meeting
You can suggest topics by posting a comment. Let us know if you want to lead this meeting.
Channel: #themereview | Time: 2017-10-10 at 17:00 UTC 17:00 UTC.

Tuesday, 17th of October – No meeting

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

 

 

  • Monitor open Theme Review meta tickets
  • Revise documentation and requirements
  • Occasional posts to remind authors of upcoming major theme changes (core changes)

Every 6 months:

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