Mobile Team Update – February 11th

WordPress iOS and Android version 14.2 is available for testing. 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: Inserter and Image block UX improvements, fixed sharing media from other apps on Android, and upgraded RN version which is yielding better performance.
  • Full Site Editing: Group block shipped. First set of Starter Page Template designs reviewed. Button block and gallery uploads are close to shipping. Made progress on column and cover blocks.
  • Other Projects: On iOS, mobile/desktop preview improvements, WKWebView migration, offline support for pages, and media editing basics were completed. On Android, work continued on the Material theme updates, media editing, and offline pages support.
  • Infrastructure: We continued to improve the development tooling.

#mobile

February 6 2020 Support Meeting Notes

2020-02-06 forum support team meeting

https://wordpress.slack.com/archives/C02RQC6RW/p1581008447159700

  • quick summary of the forum ticket scrub
  • all OK with the international fora
  • discusson of javascript issues when http/https mismatch occurs on sites. Will Chrome 80 fix this?
  • open floor:
    • macmanx proposes that Otto write guidelines for moderators and publish them on make.wordpress.org/support. There’s been a lot of pushback on moderation lately.
    • jnash proposes a capability to allow some users to “moderate” the spam queue (or at least, tag items as spam and pending). This led to discussions about whether we just
    • need more moderators. jnash is creating a trac ticket to further the discussion

#support

Plugin Review Team: 10 February 2020

Plugin Status Change Stats

  • Plugins requested : 165
  • Plugins rejected : 11
  • Plugins closed : 20
  • Plugins approved : 63

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 715
  • → (older than 7 days ago)** : 618
  • → (2020-01-20 – 2020-01-27) : 77
  • → (new; not processed or replied to yet)* : 20
  • → (pending; replied to)* : 695

HelpScout Stats

  • Total Conversations: 307
  • New Conversations: 204
  • Customers:272
  • Conversations per Day: 38
  • Busiest Day: Monday
  • Email Conversations: 204
  • Messages Received: 362
  • Replies Sent: 444
  • Emails Created: 131
  • Resolved: 176
  • Resolved on First Reply: 26%
  • Customers Helped: 267
  • Replies per Day: 29
  • Closed: 264

#plugins

Design team update February 7th

The design team is busy working on 5.4 and lots more. There is a focus list for things this releasee.

On Wednesday the design team met at the usual time of 19:00 UTC. Monday and Tuesday saw triages run also in #design.

The Gutenberg design updates continue and you can catch them here and here.

Calls for involvement

Gutenberg continues to need people to give feedback and create designs.

If you are having a WordCamp that has a design contribution table, please reach out in #design so you can be added in future updates.

WordCamp Asia will see a design contribution table, everyone is welcome.

#design

Plugin Review Team: 03 February 2020

Plugin Status Change Stats

  • Plugins requested : 152
  • Plugins rejected : 69
  • Plugins closed : 39
  • Plugins approved : 57

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 703
  • → (older than 7 days ago)** : 604
  • → (2020-01-20 – 2020-01-27) : 88
  • → (new; not processed or replied to yet)* : 28
  • → (pending; replied to)* : 675

HelpScout Stats

  • Total Conversations: 355
  • New Conversations: 257
  • Customers: 339
  • Conversations per Day: 44
  • Busiest Day: Friday
  • Email Conversations: 257
  • Messages Received: 307
  • Replies Sent: 449
  • Emails Created: 195
  • Resolved: 139
  • Resolved on First Reply: 26%
  • Customers Helped: 325
  • Replies per Day: 37
  • Closed: 291

#plugins

January 23rd Support Team Meeting Summary

Read the meeting transcript in the Slack archives. (A Slack account is required)

Additions to the guidelines

Most of this weeks meeting time was taken up by discussions about amendments to the support guidelines, and a very good discussion ensured relating to changes in guidelines relating to the use of links in plugin and theme related support topics.

As the subject can be hard to cover, a separate post will be made outlining the changes, and how they may (or may not) affect the average user.

Checking in with international liaisons

Representatives from our non-English parts of the community in Italy, Netherlands, Russia, Greece, Sweden, Brazil, Bangladesh, and India were present this week, and helped broaden our horizones.

Reminder that if you are from a non-English speaking part of our community, we would love to hear from you, as shared experiences are worth more than we can describe!

#support

Mobile Team Update – January 28th

WordPress iOS and Android version 14.1 is available for testing. 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 roll out on Android is in the green and some fixes landed in the image block, the text blocks UI, the rich-text formatting and list block controls
  • Full Site Editing: The Shortcode block shipped and Gallery style improvements and SPTs phase 1 technical tasks are considered done. Progress was made on the Gallery upload, the Button, Column and Cover blocks.
  • Other Projects: Completed Vision accessibility and post logic improvements and shipped the Me and Create FAB IA changes on Android. Reblogging on iOS and WKWebView migration are nearly ready to ship while progress has been made on mobile / desktop previews and on Dark mode / material components for Android. Kicked off Media editing on Android and offline support for pages.
  • Infrastructure: Improvements to our build and development tooling related to WP screenshots and WP Mocks.

#mobile

Plugin Review Team: 27 January 2020

Plugin Status Change Stats

  • Plugins requested : 164
  • Plugins rejected : 7
  • Plugins closed : 13
  • Plugins approved : 56

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 768
  • → (older than 7 days ago)** : 665
  • → (2020-01-20 – 2020-01-27) : 85
  • → (new; not processed or replied to yet)* : 38
  • → (pending; replied to)* : 730

HelpScout Stats

  • Total Conversations: 259
  • New Conversations: 184
  • Customers: 230
  • Conversations per Day: 32
  • Busiest Day: Wednesday
  • Email Conversations: 184
  • Messages Received: 270
  • Replies Sent: 349
  • Emails Created: 117
  • Resolved: 138
  • Resolved on First Reply: 30%
  • Customers Helped: 223
  • Replies per Day: 26
  • Closed: 198

#plugins

WCEU 2020 – Leave no Contributor Behind

The organising team for Contributor Day at WordCamp Europe in June this year needs your help. The team would like to do two things:

  1. Increase the value that new attendees get from Contributor Day
  2. Increase the long term benefit to the WordPress project from onboarding new contributors

What’s the Problem We Are Trying to Solve?

Many teams see a good start first thing in the morning on Contributor Day, with an introduction and lots of enthusiasm. Sometimes this can tail off as new contributors get stuck, can’t find relevant tasks to get involved with, or can’t get help because experienced contributors have moved on to working on their own tasks.

Contributor Day presents huge potential but often the number of returning contributors isn’t as high as it could be. Although we don’t have numbers for this, that’s the feeling that experienced contributors have communicated in the past.

It would be great for the WordPress project to gain more regular contributors as a result of attending a Contributor Day.

Let’s Plan for Long Lasting Contribution

There are three aspects to improving the retention rate of new contributors on a Contributor Day:

  1. Better planning prior to the event
  2. Better support during the day for new contributors
  3. Better follow-ups in the days after the event

The organising team is planning to contact the team reps from each of the teams that make up WordPress and ask them to help facilitate this plan. WCEU Contributor Day is a great opportunity to do this at the team levels due to the high number of experienced contributors in attendance.

1. Better planning prior to the event

An example of a problem that can be reduced with some prior planning is the fact that all the “good first bugs” often get taken within a short period of time, leaving new contributors struggling to find tasks to work on. With a small amount of planning in the weeks prior to WCEU, it should be possible to get a higher number of good first tasks lined up and ready to be worked on by new contributors at Contributor Day.

Team reps

  1. Please ensure the content of your “Getting Started at a Contributor Day” handbook page is up to date (example from the Polyglots). This page should give an idea of what the team works on during Contributor Days. If you don’t have such a page, please create one. These links will be published on a specific page for attendees, so the sooner you can confirm you have it, the better. 
  2. To maximize the value for new contributors, please collate tasks that both new and existing contributors can work on during the day (for example your “good first tasks” list). This list needs to be fairly detailed and be published on the WCEU website a week prior to the event.
    Example of how the Community team does this:
    Call for ideas
    Plans for the day

2. Better support during the day for new contributors

Some teams run short introductory sessions on Contributor Day and it would be great to have more of these in 2020. This could be a session repeated a few times during the day to reach as many new contributors as possible.

Team reps

If your team needs it, can you plan an introductory session to help onboard new contributors to your team? It doesn’t need to be long, around 10 minutes with a few slides is ideal.

In addition, it would be great for existing contributors to help out new contributors who may get stuck or run out of tasks on the day. Identifying existing contributors who will be in attendance and happy to do this should make the day more valuable for everyone.

The WCEU 2020 contributing team wants to move away from having one or two team leads and instead having a team of experienced contributors functioning as mentors to help and guide new contributors.

3. Better follow-ups in the days after the event

During Contributor Day and the days immediately following it, the project sees contributions from new contributors that typically need some guidance. For example, patches that need testing and feedback, translations that need approval, or just a general check-in to see how a new contributor is getting on.

Team reps

In order to help maintain enthusiasm, it would be great to have a plan to ensure new contributors get feedback on their initial contributions. This takes different forms depending on the team, so please think about how you can support new contributors in the days after the event.

There will be a room available for use as a Contributing Area during the main WordCamp event. All teams are welcome to share this room in order to carry on contributing or helping out new contributors.

Thank You

Thank you for helping increase the value of WCEU Contributor Day for everyone!

If anyone (existing or new contributors) has any other ideas about making the event more valuable, please leave a comment.

The WCEU 2020 Contributing Team
Abha, Aleksandar, Francesca, John, Laetitia, Michael

#contributor-day

Design team update January 24th

The design team is focusing on 5.4 as work on this release begins. Lots of great things happened this week including 2 triages and a team meeting.

On Wednesday the design team met at the usual time of 19:00 UTC. Monday and Tuesday saw triages run also in #design.

There is a proposal list of things to focus on for 5.4.

Calls for involvement

Gutenberg continues to need people to give feedback and create designs.

If you are having a WordCamp that has a design contribution table, please reach out in #design so you can be added in future updates.

#design