Currently
- 70 new tickets are waiting for review.
- 60 tickets are assigned.
- 22 are approved but are waiting to be made live.
Plugin Review Team Status – 18 March 2019
Plugin Status Change Stats
- Plugins requested : 176
- Plugins rejected : 9
- Plugins closed : 25
- Plugins approved : 105
Plugin Queue Stats (current)
- Plugins in the queue (new and pending) : 591
- → (older than 7 days ago) : 527
- → (2019-03-11 – 2019-03-18) : 44
- → (new; not processed or replied to yet) : 17
- → (pending; replied to) : 574
SupportPress Queue Stats
- Total open tickets : 8
- → (with no activity in last 7 days) : 1
- Within defined 7 day time window:
- Total : 328
- Closed : 324
- Open : 4
Design Team Update – March 15th
Weekly meetings continue every Wednesday at 19:00 UTC in #design on Slack, our daylight saving time changes the beginning of April. The team continues to also run triage sessions 17:30 UTC.
- Meeting notes:
- Gutenberg phase 2 update notes:
Some highlights from the last fortnight:
- Accessibility walk through video for navigation block.
- Open invitiation to become a researcher.
- Test simple responsive controls.
- There will be an AMA walkthrough of ‘Site building research‘ on Monday at 19:00 UTC in the #design Slack channel.
- Design triage is focusing on Gutenberg for the entire month of March.
- The ‘ui-feedback’ and ‘ux-feedback’ labels are now combined into one ‘needs-design-feedback’ label within Trac. Read the background post to this change.
March 14th Support Team Meeting Summary
General announcements
First up, just a reference to a cross-posted article on organizatory tasks in the WordPress.org community in general, which is worth a read, it’ll get some more details moving forward though, you can find it at https://make.wordpress.org/updates/2019/03/12/strengths-and-challenges-organization/
Second on the agenda, last call for strings on Health Check, I’ll start putting them in tonight/tomorrow. We’ve already got some valuable copy editing input yesterday as well, and a huge shout out to those of you who have been working on that!
The ticket for it can be found at https://github.com/WordPress/health-check/issues/256 which also has the link to the google doc for colaborative commenting
How we do attendance
After a bit of discussion, we’ve come to the conclusion that although attendance was useful previously, to help ensuring important information was shared and procedure changes were acknowledged, we now have better tools for this.
Attendance also had some negative effects, causing double pings on summary posts, and implied only those who attended the meetings had a say. Input is still very valuable, and appreciated, on our make/support posts, and outside of meeting hours as well.
Checking in with international liaisons
We had representatives from the Netherlands, Russia, Sweden, Greece, India, Italy and Spain.
If you’re from any other part of the world, and would like to participate, let us know how things are going, or just have questions or concerns we can help with, please join our weekly meetings and we would love to meet you!
Open floor
We’re still hoping to organize a form of Support appreciation day, and the pre-planning is happening in a google doc page. If you would like to help organize or get this going, please reach out either via DM on slack to @clorith, or leave a comment on the post relating to it.
Read the meeting transcript in the Slack archives. (A Slack account is required)
Mobile Team Update – March 12th
WordPress iOS and Android version 12.0 will be available for testing later today. Sign up here to join the beta program on iOS or follow this link on your Android device, tap on Become a beta tester.
Highlights for the last two weeks:
- Block Editor (Gutenberg mobile): Some important bug fixes on the v1.0 while in beta rollout.
- Post Filter improvements in Android continues.
- Offline Support: On iOS we are migrating offline messages from Alerts to Notices.
- Infrastructure: Migration to CircleCI completed, more work on end to end testing infrastructure.
Theme Review update for March 11, 2019
Plugin Review Team Status – 11 March 2019
Plugin Status Change Stats
- Plugins requested : 161
- Plugins rejected : 7
- Plugins closed : 90
- Plugins approved : 106
Plugin Queue Stats (current)
- Plugins in the queue (new and pending) : 580
- → (older than 7 days ago) : 525
- → (2019-03-04 – 2019-03-11) : 40
- → (new; not processed or replied to yet) : 10
- → (pending; replied to) : 570
SupportPress Queue Stats
- Total open tickets : 20
- → (with no activity in last 7 days) : 1
- Within defined 7 day time window:
- Total : 277
- Closed : 275
- Open : 2
Accessibility team update for March 9, 2019
- Health Check plugin review: 9 issues opened, 7 already fixed.
- Accessibility automated testing tools: The project is close to be publicly released and the team is now moving it into the WPAccessibility GitHub repository.
-
Trac tickets triage:
- 24 Tickets milestoned in 5.2, the next major release (30 last week), all assigned to an owner.
- There is some good progress on at least other 3 of the most tricky tickets.
- 8 Tickets committed this week.
- Gutenberg accessibility issues triage: the accessibility team is going to give a triage document to the #core-editor team to help to prioritize the issues. However, both Accessibility and Editor teams are a bit short in term of developers availability so the idea is to handle 3-4 issues per week if possible.
- Gutenberg User Documentation: awaiting feedback from Docs team.
Last meeting recap:
March 7th Support Team Meeting Summary
General announcements
The first iteration of user documentation for the new block editor is now live, either via https://wordpress.org/support/article/wordpress-editor/ but also from the Support page under the title “Writing Posts” for general discovery.
As some may have noticed recently, we’ve lost a lot of wonderful German contributors. In light of this we’ll be reaching out to the existing moderators there to see if anyone would want to be the liaisons between our global team and their local one, as well as how things are going, and what we can do to help.
If you are a part of the German community and would like to help out there, or have questions, feel free to reach out. This also goes if you’re from another community and would like to get more involved, we’d love to welcome you into our midst!
Another subject in this weeks meeting is burnout, and because @macmanx puts it better than I, here is a quote:
When we say “please take the time you need” (or similar) whenever you mention burn-out or other difficulties contributing to the forums, we mean it sincerely in a “I care about you” fashion, not a “go away” fashion.
When you tell us you need to step away, please don’t expect us to ever push back.
Every contribution you make is valued and appreciated, but we want you to put your needs first. We can guarantee that we’ll do our best to stay on top of things while you’re out, and that the forums will still be here if you want to come back. What we can’t guarantee is your health and happiness, and that’s why we’d rather you always put that first.
If you need to step away, please do so. We want you to take care of yourself, and we’ll look forward to when you’re feeling ready to return.
On a somber note, long time contributor and community member Alex Mills passed away recently. As one of his requests, we would love to help keep his plugins going, someone is taking ownership of maintaining them already, but if you wish to help out in supporting one or more of them, it would be very much appreciated.
WordPress 5.1
We’re seeing an increase in plugin compatibility issues leading to broken media libraries. We’ve been unable to pinpoint the source, as it’s happening with many plugins, so this may be bad caches, hopefully we’ll learn more and have something a bit more solid, but worth noting.
Checking in with international liaisons
Members of the Italian, Swedish, Greek, Spanish, Russian, Dutch and Indian communities were present for this weeks discussions.
The Russian team has some intercommunication troubles they are working out, and we’ve offered to assist in any way we can if they wish it.
Open floor
Reviews with links in them are often frowned upon, as they are at times used for spam, but some users do it without being aware that it’s bad at all.
Based on this, if a review contains a link, we’ll now do the following:
- Remove the link from the review (but leave the review if it’s legitimate)
- Leave a user note of the action
- Post a response letting the reviewer know that links shouldn’t be used in reviews.
This way we educate users, without causing distress or anger. This of course does not apply to obvious spam entries, which get treated like any other spam.
In other news, the WordPress 5.0 retrospective kickoff was posted over at https://make.wordpress.org/updates/2019/03/01/5-0-release-retrospective-kickoff/
Read the meeting transcript in the Slack archives. (A Slack account is required)