Coordinating Devchat

Running Weekly Meetings 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 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 The WordPress community has its own Slack Channel at logs.

Top ↑

Devchat @here announcement 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.

Top ↑

Daylight Saving Time (DST) Daylight Saving Time (DST)

Since the United States is generally one of the last locations to adjust to DST worldwide, the weekly devchat time gets adjusted after the US begins and ends DST. The devchat time changes the first devchat after the DST change, unless that week is a major national holiday or WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more..

The process to adjust the devchat time change is:

  1. Publish an update alerting people to the time change (example) at least two weeks before the US DST time change
  2. After the devchat time changes
    1. Update the time on the Meetings page entry for devchat (edit here)
    2. Update the time on the Weekly Developer Chats page
    3. Update the time on the Core welcome page

Last updated: