We had a fairly productive meeting with loads of good ideas. Read the Slack transcript here.
Ideas proposed for the next hangout:
- Working with the customizer, possibly discussing how best to implement options such as slides.
- Using core hooks.
The team voted to automatically remove a reviewer if they have not added a comment in the ticket for 2 days after being assigned as the reviewer on a ticket. The ticket would then go back to the top of the queue so that another reviewer could pick it up.
Docs: The discussion evolved into improving the handbook and making things much clearer for theme authors and new reviewers. One proposal is to make February “theme handbook review” month, in which we spend time working on and improving the handbook.
Mentoring: There are a number of people who would like to bring the mentorship program back (+9 in favor). However, the concern is having enough experienced reviewers with the time to mentor new reviewers. If you’re a theme reviewer who would like to mentor, please comment below so that we can have a general count of who might be interested.
Priority queue: +13 votes were registered in favor of the following priority queue idea:
2) Priority queue for theme authors who have had less than 5 issues in their last theme review and they would be removed if they have more than 5 issues in a review. The number of theme authors on the list may be small in the beginning but this will be a goal for theme authors to work to and provide additional motivation to make sure the themes are up to standard. This should be relatively easy to implement with a custom report and perhaps some customisation to the assign review button.
Improving theme author experience
@ilovewpcom is in charge of working on the “theme author experience” project (just came up with that name). If you’re interested in helping out with making the uploading/reviewing experience better (from a theme author perspective) or sharing ideas, ping him on Slack.
The last meeting was on November 10, which was a short meeting and there was a bit of confusion about the time change.
As I was unwell one time and recovering from travel we have not had any meetings.
The next one will be December 22. We will be keeping the time at 14:00 UTC as not every country changes their clocks and this UTC time works for everyone.
Channel: #themereview | Time: Thursday at 14:00 UTC 14:00 UTC
The agenda for the 22th December will be
- Short update from the contributors what they have worked on.
- Define goals for the next meeting.
- Discuss any open issues and/or pull requests that need attention.
We need help with the following items.
If you want to to test out the current
WordPress-Theme sniff you need to download it from our fork. https://github.com/WPTRT/WordPress-Coding-Standards
There is documentation how you can integrate it with your favourite IDE.
If you are interested in writing sniffs, please DM me on Slack with an issue that you would like to work on and I can help you get started and answer any questions.
Pinging @poena, @frankklein, @jrf, @shinichin, @miyauchi, @iamdmitrymayorov, @jmichaelward, @marius2012, @djrmom
If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.
The summit is approaching and we need to have a series of discussion points. Over this week, lets get points and then vote in next week’s meeting.
From the make.community blog:
1) Each make.wordpress.org project team creates a list of relevant topics/issues which are relevant for the progress of the team and the WordPress open source project as a whole, prioritizing topics or tasks which are sensitive enough to specifically require in-person discussion.
2) Each team rep will post their final discussion topic list on the Community Summit blog: https://make.wordpress.org/summit/. Deadline: December 20th
- clarify that authors need to use the customizer api to add the upsell
- Themes should not display obtrusive up-selling
demo and starter content requirements.
- define what placeholder content is
- Anything that is shown that you cannot pull from the user’s install ( 10 thumbsup )
- Capability check
- starter content
- must use core
- exception is: images ( 9 thumbsup )
- January 7-8
- Livestream focus: tools
A Slack account is needed to view the archives.