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

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

August meeting agenda

The Theme Review Team holds a monthly meeting with an agenda and we encourage all members to attend.

Channel: #themereview | Time: Tuesday at 17:00 UTC 17:00 UTC

Topics to discuss

Microformats

https://wordpress.slack.com/files/joyously/F5SFNUWG7/Microformats_-_the_hidden_feature_bug_in_themes

Gutenberg

Can themes create custom blocks?

Page on front

Your feedback is needed

Page on Front “Lean UX Canvas”

Team moderators

  • Removed inactive moderators
  • Suggesting new moderators

Tasks for reviewers, moderators and team leads

Scheduling tasks?

https://wordpress.slack.com/files/poena/F6TSBCZNC/TRT_tasks

 

 

 

July Meeting Agenda

The Theme Review Team holds a monthly meeting with an agenda and we encourage all members to attend.

Channel: #themereview | Time: Tuesday at 17:00 UTC 17:00 UTC

Topics to discuss

Community Behaviour / Code of Conduct

Proposal: WordPress Community Conduct Project

Name collisions

Currently the WordPress.org Theme Updates API only uses the theme slug to check for updates. This can cause conflicts if a theme outside of WordPress.org repo has the same theme slug. The two main issues are:

  1. Name collisions are bad for end users if they update to different theme.
  2. The number of active installs have an affect on the position of theme on the popular page.

In the past we have decided not to police theme names other than “WordPress” and “Theme” which have been added as checks to the upload process.

The root cause for this issue is that the WordPress.org Themes API only checks the theme slug when checking for updates or tracking number of installs. The Core Ticket for this is #14179-core. The core track ticket has been opened a number of years ago and it is not going to be fixed unless we get buy in from the core and meta teams.

There are a few short term solutions that we can implement but they require support from the meta team. The meta ticket for this is #2114-meta. These solutions are

  • Change the algorithm of the popular page so that it is not so heavily dependant on number of installs.
  • Deduct the initial number of active installs from the current active installs. This does not help if two themes are gaining new users together.
  • When measuring the number of active installs compare the author field. The number of installs may be slightly off for themes that have been transferred from one author to another but these numbers should be minimal as they would be only users running older versions of the theme.

The solution that we can implement as of now is: If any theme name has any more than 500 active installs then that theme would need to be renamed.

  1. This would not retroactively apply to existing live themes. Removing the themes would affect the users which we do not want. The short term solutions will fix this for the existing themes.
  2. This wouldn’t apply in those cases where the theme author has had the theme released for a while and a quick Google search doesn’t pull up alternatives.

Monthly meeting with meta team

Currently there are 44 open meta tickets for the components “Theme Directory” and “Theme Review”

By having a monthly meeting we can track the progress of these tickets and define which ticket should be prioritized.

Discussions on improvements outside the meetings

There have been a number of discussions in the Slack #themereview channel which have lead to turning in circles. Unless there is a meeting these discussion will not go anywhere. If there is a topic to discuss please mention it for the next meeting.

The Theme Review process is not perfect. Here are a list of projects in addition to the meta tickets mentioned about that are known but have not had anyone to lead them.

The structure for solving the problems that we would like to try is

  • In the meetings we can discuss if it is this a problem that needs to be addressed (regardless of the team that addresses it)?
  • If yes then we collect proposals for addressing it.
  • The we decide which one of these proposals should we pursue?” and then commit to pursuing the winning proposal

Mentoring

@thinkupthemes has created a list on the mentor’s availability.

https://docs.google.com/spreadsheets/d/1ClUWZoNIIqKYmdgb08QRNWUmgebhxM-f3mm-9FqC6Kw/edit#gid=0

#14179-core, #2114-meta