X-post: The Developer’s Guide to Supporting Your Themes – Video and Slides

X-comment from +make.wordpress.org/support: Comment on The Developer’s Guide to Supporting Your Themes – Video and Slides

X-post: The Developers Guide to Supporting Your Themes – A Support Workshop

X-comment from +make.wordpress.org/support: Comment on The Developers Guide to Supporting Your Themes – A Support Workshop

X-post: Community Conduct Project – Kick off meeting scheduled for 17:00 UTC on the 5th September 2017

Community Conduct Project – Kick off meeting scheduled for 17:00 UTC on the 5th September 2017

Meeting notes – 2017-07-25

Items brought up:

  • Community behavior – code of conduct.
    • The channel can often get disruptive with uncalm discussions.
    • Better communication between reviewers, mods, and leads.
    • Some people expect the team leads to make a decision in less than 7 days.
  • Name collisions
    • The theme uploader has been changed to not allow new themes from being uploaded if it detects more than 50 active installs using that same slug.
    • The limit can be changed later if necessary.
    • Only new themes uploaded after July 25, 2017 are affected.
  • Meta meetings
  • Mentoring

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