At first, thank you all for your active participation in this meeting.
The meeting was held based on this meeting agenda.
Channel: #themereview
Notes Taken: @kafleg
Time: Tuesday, March 09, 2021, 15:00 UTC
Meeting agenda
- Weekly updates
- Dashboard and statistics proposal
- Meta 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. Ticket Triage
- Open Floor
1. Weekly Updates
Currently 48 new parent themes and 13 new child themes are waiting for review.
The waiting time is just over 2 weeks.
In the past 7 days,
- 311 tickets were opened
- 327 tickets were closed:
- 295 tickets were made live.
- 19 new Themes were made live.
- 276 Theme updates were made live.
- 4 more were approved but are waiting to be made live.
- 28 tickets were not-approved.
- 4 tickets were closed-newer-version-uploaded.
Number of active reviewers this week: 6
HelpScout Stats
In the past 7 days,
- Email Conversations: 14
- Messages Received: 21
- Replies Sent: 14
- Emails Created: 0
- Resolved: 10
- Resolved on First Reply: 80%
Please check the weekly updates details here.
Thank you all the reviewers who helped this week.
2. Dashboard and statistics proposal
This agenda was based on this proposal. During the meeting we discussed what statistics we need from themes team. The two major question we raised during meeting was,
- What metrics would your team want to track?
- Would any team have a need for private stats, or could it all be open and transparent?
The team agreed that for theme reviews, it would be beneficial to have statistics about why tickets are closed as not approved. This would help the team learn where to focus their efforts and improve documentation.
@aristath already commented in the post.
-There is no benefit to the team if the statistics are only the numbers of opened or closed theme tickets, since this information is already available on Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..
-As long as any information about suspensions or delisting is anonymized, the dashboard can be public.
@joyously Asked if the statistics are for the theme directory or for theme reviews.
There are many things that could be tracked for the theme directory, that could help highlight room for improvements:
- Number of theme previews
- Keywords used in theme search
- Usage of Tags in the theme filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.
You can read the proposal and give your feedback and suggestions.
3. Meta Ticket Triage
We checked meta tickets related to theme reviews and the theme directory. We checked and discuss the following tickets,
a) Remove theme reviewer if no comment in 48 hours – https://meta.trac.wordpress.org/ticket/2405
We already have 7 days inactivity period, thus we decided to close this ticket as maybelater.
b) Add PHPCS PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. to theme upload process – https://meta.trac.wordpress.org/ticket/2902
This is still ongoing with the theme review action. We decided to keep it open.
c) Display theme position in the review queue – https://meta.trac.wordpress.org/ticket/2444
@aristath said that, this is nice-to-have but definitely not a priority. We kept that ticket as it is.
4. Open Floor
There was few question about the theme review process and we sorted out the confusion.
You can read the entire meeting discussion via this link.
Any comments and discussion can be done via the below comment box.
#team-meeting, #themes-team
