Dev Chat Update – Timezones and Daylight Saving Time

Having discussed the following in both dev chat conversations last week this post is to bring you up to date with some small tweaks being made to bring both dev chat meetings into closer alignment.

The chat that happens at 0500UTC is more accessible to APAC region but has felt like it’s been appended to and has less weight than the 2000UTC meeting. After discussion last week in both meetings, the following changes are being made to balance that weight, and to also hopefully help encourage more participation in the newer meeting.

The 0500UTC chat will move 24hours earlier to Wednesday so both chats will fall on the same day.

That change has been reflected in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. here and in the Weekly Developer Chats page (the calendar update is in progress). Please reply in the comments below if there are any other areas in which this change needs to be updated (on the blogblog (versus network, site) or elsewhere).

This change clears the path to be able to refer to the dev chats by time rather than by region and hopefully removes blockers from anyone attending or wishing to attend who may have felt they were on the margins because they are based outside of APAC.

However, what is yet to be confirmed is how we respond to daylight saving changes. Whether the UTC timing of the chat shifts to stay consistent with local time (as it has done in the past), or whether the timing of the chat stays consistent with UTC and therefore changes locally when the clocks change.

The decision on this should be made before the next daylight saving changes take effect. The timeline for those changes is below in order they occur. Also noted is how keeping consistent with UTC will affect the timing of dev chat.

  • New Zealand – Sept 27 2020 – Later by 1 hour
  • Australia – October 4 2020 – Later by 1 hour
  • UK/EU – October 25 2020 – Earlier by 1 hour
  • US – November 1 2020 – Earlier by 1 hour

So, now here’s the question: Do we keep the time consistent with UTC? Or local time?

Props @peterwilsoncc for proofreading.

#apac, #dev-chat

Setting the structure and an agenda for APAC-friendly devchat

@francina‘s proposal for APAC-friendly devchats attracted interest from commenters on every continent. I approached them recently to get their thoughts on moving forward.

Based on that advice, I propose a first meeting to set up these devchats and schedule them on the #core channel on Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at

A look at all the team meetings in the Meeting Calendar shows an opening on Thursdays at 15:00 AEST – this replaces the APAC Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Session which will be rescheduled.

So let’s meet this week: Thursday, June 18th, at 15:00 AEST.

Please comment below with your thoughts on discussion topics, ongoing structure and agenda or anything else that seems relevant.

See you on Thursday!

Edit: This post has been edited to bring forward the start date by a week — @peterwilsoncc.

#apac, #dev-chat, #meeting-calendar, #proposal

APAC Triage and Bug Scrub Sessions

Living in APAC timezones can be difficult. From waking up at 3am for meetings, to flying 20+ for WCUS or WCEU (WCAsia is coming to fix that!), to hearing “what’s it like living in the future?” jokes for the millionth time. One thing that shouldn’t be hard is contributing to WordPress, and it’s time to make that even easier, with APAC-friendly triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub sessions.

You may have already seen GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. meetings happening every second week for the last few months, but starting Thursday at UTC 0600, we’ll alternate each week between working on WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and Gutenberg! This week, join in the fun in the #core SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel for a WordPress Core bug scrub. Next week, the party will be in the #core-editor Slack channel, for a Gutenberg bug scrub. 🎉

The meeting lead will pick a report to work through, but if there are particular issues you’d like to get more eyes on, or you have a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing./PR that you’d like reviewed, this is the place to bring it up!

#apac, #bug-scrub, #core, #core-editor, #gutenberg, #triage