Coordinating Devchat

Running Weekly Meetings

The general flow of preparing for, hosting, and summarizing devchats is as follows:

1. Publish an agenda (example) at least 24 hours before the scheduled devchat time and including the relevant release number, “devchat”, and “agenda” tags to ensure it appears in relevant searches/filters elsewhere on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
2. Script your agenda topics so you can copy/paste into devchat (example).
3. Publish meeting summary (example) ideally within 24 hours after the completion of devchat and including the relevant release number, “devchat”, and “summary” tags to ensure it appears in relevant searches/filters elsewhere on Make/Core.

As you’re writing agenda and summary posts, keep in mind the Post & Comment Guidelines.

Devchat opening / closing tags

At the beginning of devchat, include a <devchat> opening tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) (example). At the end of devchat, include a </devchat> closing tag (example). This makes it easier to find the devchat afterwards in the SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. logs.

Devchat @here announcement

In order to generate the @here channel notification to start the devchat meeting in #core, you’ll need to use the /here command as @here has been disabled. If you do not have the access to use the /here command, then ask for the ability in #meta with an explanation that you’re helping coordinate devchat in #core and access should be added to your Slack account.

Devchat timing

Devchat’s timing doesn’t change with DST and it operates regularly at 05:00 UTC and 20:00 UTC on Wednesdays as noted on the Weekly Developer Chats page.

Devchat used to be once a week and its time would adjust as Daylight Saving Time (DST) adjusted around the world. This was originally desired as a way to keep the devchat meeting at the same time across timezones to allow folks to regularly plan on when to attend. However, the process for updating the meeting time as DST changed became more time-intensive than desired and with the addition of a second devchat each week there are now two conversations that folks can attend. With that, the change was made.